https://www.ejabberd.im/forum/28793/clustering-config en https://www.ejabberd.im/forum/28793/clustering-config#comment-67475 <p>Disclaimer: I'm not a clustering expert, so I just comment what I know in case they give you ideas to solve your problem.</p> <p>If one node is defined as master and the other is slave, try to stop first the slave, then the node.</p> <p>The "session" mnesia table keeps an element per each XMPP client session: erlang pid, user jid, session priority... So, this table is only relevant while the server is online; when it stops, the table contents are useless. I guess that's why its contents aren't dumped. That table may be replicated across nodes to allow the nodes to act as a cluster.</p> <p>If a node stops, and the other keeps receiving new session connections, then its table contents deviate from the other node. When both synchronise again, their contents don't match. But as I mentioned, once the cluster shutdowns, that table content is useless.</p> <p>Regarding your error report, it complains that the "session" table definitions, not the content, are different. Looking at them, there are just a pair of changes, just a pair of numbers, but I don't know what exactly refer to.</p> Fri, 19 May 2017 10:00:02 +0000 badlop comment 67475 at https://www.ejabberd.im