ejabberd 16.03 - Presence/Cluster/sm_db_type sql Issue

Hello,

We recently upgraded to ejabberd 16.03 and decided to make use the ability to store session information in the database. We also use ejabberd clustering.

The issue is this: if users are connected to different nodes, they will not receive presence packets for each other or have the ability to message.

The cluster configuration appears successful as I can see both nodes listed in the admin under "Running Nodes".
The sm_db configuration appears successful as I can see records being inserted and deleted from the sm table.

Still, there seems to be something off.

Example:
User A connects to Node 1
User B connects to Node 2

Neither user will receive a presence packet. If they do, however, connect to the same node, they will see presence packets.

I was thinking maybe the clustering configuration needs to be different when using the database for sessions persistence, but I wouldn't know what to change.

Any help or thoughts would be appreciated.

Syndicate content