I will put the scenario
I have two machines in current cluster. The idea is that in case load
increases i will add another instance to this cluster making it to 3
machines. Current configuration
* A load balancer in front of two instances.
* Each machine is running complete jabberd2 softwares (router, sm, c2s
+ modules SOs).
* connected to a external DB cluster.
I am stuck with problem where "router" has to share routes. Assume
following scenario
* Load balancer can forward incoming request from "User1" to
"Machine1" and "User2" to "Machine2"
* Incase "User1" wants to communicate with "User2" that means both
"router" has to talk to each other.
Are you suggesting, I shall run single instance of "Router" and run
multiple instance of other components (SM, S2S & C2S). In this case,
"router" will be under load and will become critical ? How do we load
balance "router" ?
On Mon, Aug 4, 2014 at 5:10 PM, Tomasz Sterna <to...@xiaoka.com> wrote:
> Dnia 2014-08-04, pon o godzinie 16:49 +0530, Kumar Deepak pisze:
>
> > Does Jabberd2 support clustering ?
>
> Depends how you define clustering.
>
> jabberd2 supports load-balancing of components.
>
> You can run many instances of c2s and sm servicing one domain.
> You can run many instances of s2s component distributing s2s traffic
> load.
> Also, legacy components can be load-balanced - i.e. you can connect many
> instances of the same transport for same transport domain.
>
>
> > Can please point me to relevant links ?
>
> What do you mean?
> There isn't anything to document or describe, besides what I just
> said. ;-) It just works...
>
> I could point you to the code implementing it, but I doubt was that your
> point? ;-)
>
>
> --
> Tomasz Sterna @ http://abadcafe.pl/ @ http://www.xiaoka.com/
>
>
>
>
