ejabberd - Comments for "S2S Session management"

Federation is by design pure

mremond — Tue, 29 Sep 2015 07:19:58 +0000

Federation is by design pure XMPP. You cannot make Erlang calls over federation. As you see, federation is no substitute for clustering.

Hi, thanks for responding!

Nelson — Thu, 24 Sep 2015 19:52:13 +0000

Hi, thanks for responding! I'm definitely talking about federation. Let me rephrase and give a specific use case.

1) I have two XMPP servers with different domains: domain1.com and domain2.com
2) I have to users: user1@domain1.com and user2@domain2.com
3) Messages between user1@domain1.com and user2@domain2.com work perfectly (both chat and muc)
4) From domain2 XMPP server, I need to know the online status of user1@domain1.com

calling ejabberd_sm:get_user_resources(User, Server) seems to only have access to the local domain's sessions. By default, sessions are stored in mnesia?

What is the recommended way to achieve this? Is this an uncommon use case?

-Nelson

If you are talking about

mremond — Thu, 24 Sep 2015 09:19:42 +0000

If you are talking about federation, you are not talking about clustering. You have indeed to get the status by another mean. However, if your point multiple independant cluster to the same redis session management you may run into unexpected issue. We never tried that config. I am not sure what you are trying to achieve. I am under the impression that you are trying to use federation to simulate a single cluster, but I think all modules would not be aware of this intention and you would probably need to modify a lot of code in many part of ejabberd to achieve this.

Just thinking out loud ..

Nelson — Mon, 21 Sep 2015 18:40:20 +0000

Just thinking out loud .. I'm assuming odbc is not the way to go either as each cluster has it's own db. So is the solution to have a global redis server used by all clusters?