ejabberd cluster to cluster

Hi

We have a requirement where the ejabberd could be deployed across multiple regions. The way we are planning is have a cluster in each region and connect them. The architecture page shows connecting 2 clusters via "optional Federation". Is there a way we can connect 2 clusters easily. Could someone provide the steps.

Thanks,
Srikanth V

From what I remember, the

From what I remember, the nodes in a cluster communicate continually session information, so it is preferable they are in the same network, close one to others, with good network.

We've been doing something

We've been doing something similar for a number of years now: 2 systems about 70ms apart on the open Internet acting in one cluster.

As badlop says though, it's really better if they are in closer proximity to each other. For example, we usually lose the cluster once a month, forcing us to reset one of the two nodes to let it re-join the broken cluster. So really, even if on a private WAN, using a cluster is still risky due to network conditions. Clustering is really meant to work within a data center. You might be better off creating a private federation and then use some configuration tricks to fool the federation into thinking it's a cluster - but we haven't done this as our user base is very small (less than 50).

Another thing to keep in mind is to make sure you are keeping the configuration of the databases identical. You should look for some guides on the Internet that explain which ones to adjust, RAM vs disk and RAM, etc.

We're also doing external authentication for the users, using a script that accesses the postgresql database for the user and password tables. Pretty simple. The database engine handles the sync itself.

Good luck!

Syndicate content