ejabberd - Comments for "Ejabberd scaling/clustering"

Perfect, thank you badlop!

brian225 — Mon, 19 Jun 2017 22:23:00 +0000

Perfect, thank you badlop!

I assume yes. Let's think:

badlop — Fri, 16 Jun 2017 10:02:02 +0000

I assume yes. Let's think: the XMPP client will connect to one of the nodes (or the other), so whatever it connects, it must be correctly configured: accept its username+password (you accomplish that by mnesia database replication), same features (you accomplish that by having the same modules configuration in each nodes), and I satisfactory encryption (which probably means the same certificates and cert config).

Oh,one more question, would

brian225 — Fri, 16 Jun 2017 03:17:46 +0000

Oh,one more question, would the two servers need to use the same certificate/dhparam files?

Yeah, I intended on using

brian225 — Fri, 16 Jun 2017 02:49:42 +0000

Yeah, I intended on using them on VPSs so they would have a reliable network! And that makes sense, thank you!

The erlang nodes can be in

badlop — Thu, 15 Jun 2017 08:15:19 +0000

The erlang nodes can be in different machines, like ejabberd4@machine.domain.com and ejabberd5@machine2.domain.com. It's preferable if they are in a reliable network, not broad internet, but any way will work.

Regarding the exact node name, you can set it in the file ejabberdctl.cfg. Remember to do that before starting ejabberd the first time, otherwise you have to delete the Mnesia database, or convert it to the new node name.

Thank you for the reply! So

brian225 — Wed, 14 Jun 2017 11:49:49 +0000

Thank you for the reply! So in order to cluster, the nodes need to be on the same machine? I was thinking of having them run on separate machines (in case of hardware failure for instance). How would that differ?

Also, how would I achieve the name in front of the @ (ejabberd@machine.domain.com, ejabberd4@machine.domain.com)?

Let's clarify terms: - the

badlop — Wed, 14 Jun 2017 08:10:25 +0000

Let's clarify terms:
- the machine name is, for example, machine7.domain.com
- in a machine, you can have one or several erlang nodes running, each one with a different name, for example: ejabberd@machine7.domain.com, ejabberd4@machine7.domain.com
- then, in each erlang node (that is running a different ejabberd, installed in a different path, with different configuration file), you can serve several XMPP domains, for example aus.domain.com, anon.domain.com

1. In this sense, in join_cluster you must provide the erlang node name, in my example ejabberd@machine7.domain.com
2. Depending on what you want to do. Probably yes.
3. Sorry, no idea
4. join_cluster will tel mnesia of one node to sync with the other node, and it will do automatically when any of those databases change.
5. yes
6. Depends. You can even configure as hosts in ejabberd.yml "example.com", and then set DNS x.domain.com and y.domain.com, and tell your client to login to "example.com" with host "x.domain.com" and port "5222".

Sorry I can't help you more with DNS setup, better search tutorials over Internet about ejabberd (or other Jabber servers) domain setup.