We have a 2 server cluster ejabberd configured (hopefully correctly).
When a user is logged into srv2 and changes their password, the ### for words of mem changes but the words of mem on srv1 does not change or vice versa.
The user is able to log-in on both srv1 and srv2 with the new password just fine (verified by looking at the logs via which server it used to login).
When I add a new user on either web-admin portals of srv1 or srv2, the ### for records change immediately on both servers.
srv1 is setup with self as master
srv2 is setup with srv1 as master
I created a script that emails me the mnesia info on both servers every hour, and it seems srv1 is gradually incrementing in ### words of mem, but not on srv2.
- passwd : with 3316 records occupying 225899 words of mem
- passwd : with 3316 records occupying 225876 words of mem
Even after changing the table type in the web-admin portal and click submit, the numbers still do not match.
The only way I've been able to get them to match, is if I shutdown and restart ejabberd on srv2.
Does the ### for words of mem really matter?
How can I be sure that the information on table passwd is in sync?
Ok looks like it does matter.
Ok looks like it does matter. And if they do not match then of course the data is not synced properly.
I tested this on another set of dev servers and the numbers update instantaneously. Given that both dev servers are only 1 ip apart and on the same subnet.
Time to review more documentation. Wohoo.