ejabberd - Comments for "Connecting cluster nodes after channel failure" https://www.ejabberd.im/node/520 en Location of tables https://www.ejabberd.im/node/520#comment-1120 <p>Startup parameters are the same.</p> <p>All of tables has been replicated because I want users of other node to be able to send-receive messages from each other (on that node) when channel is down. It works. But after channel failure all users of other node are "online" for users of this node and messages are going to space.</p> <p>After reconnecting channel nodes are invisible from each other and webadmin console says the same.</p> Thu, 01 Dec 2005 09:18:02 +0000 defensys comment 1120 at https://www.ejabberd.im Connection Failure https://www.ejabberd.im/node/520#comment-1119 <p>I'm touching in the dark here, and I hope I don’t talk to much nonsense.</p> <p>Did you change the location of where the Mnesia tables are stored after creating the cluster? If I remember correctly all except for "schema" uses a "remote copy", if the connection between the two nodes brake, the second node won’t be able to write any offline messages to the first node where the tables are persisted to disk.<br /> Can someone please indicate the best practice to setup the replication and where to store these tables, I'm not sure if mine is setup correctly. I changed the additional nodes to be the same as the first node.</p> <p>I’m using the ODBC modules, therefore our offline messages are not dependant on the Mnesia tables, and I haven’t seen the situation you mentioned.</p> <p>The startup parameters, are they exactly the same on the two nodes?</p> <p>When you run into this situation, open the webadmin console on both nodes, do both nodes show as running from both the consoles?<br /> I’ve seen this “split brain” as well, and the only way to get them up was to restart the service.</p> Thu, 01 Dec 2005 07:09:34 +0000 tiaan comment 1119 at https://www.ejabberd.im