xmpp - ejabberd cluster: Multi-master or Master-slave -


so far i've come across -

  1. setting ejabberd cluster in master-slave configuration, there single point of failure , people have experienced issues when after fixing master (if goes down), cluster doesn't become operable again. sometimes, ejabberd instances of every slave have revisited again them working properly, or mnesia commands have in-putted again make master communicate slaves.
  2. setting ejabberd cluster in multi-master configuration of nodes can taken out of cluster without bringing whole cluster down. basically, there no single point of failure and, way in official documentation ejabberd tells via join_cluster argument expose in ejabberdctl script. however, in case, data replicated across both nodes big performance overhead in opinion.

so boils down this.

what best/recommended/popular mode in ejabberd cluster of 2 nodes should set respect performance keeping other critical factors (fault tolerance, load balancing) in mind well.

there single mode in ejabberd. basically, works describe multi-master. master-slave same setup without traffic sent second node load balancing mechanism.

so case 2 way go.


Comments

Popular posts from this blog

python - TypeError: start must be a integer -

c# - DevExpress RepositoryItemComboBox BackColor property ignored -

django - Creating multiple model instances in DRF3 -