[ejabberd] Several S2S connections from one domain to another ?
vbarat at capptain.com
Thu Oct 18 11:11:11 MSK 2012
Le 18/10/12 03:49, Evgeniy Khramtsov a écrit :
> On 17.10.2012 23:10, Vincent Barat wrote:
>> Hi guys,
>> My company (http://www.capptain.com) is using eJabberd heavily to
>> push messages to mobile devices (or web apps).
>> We have 2 XMPP domains made of 2 clusters (one for devices, and
>> the other for backend services) and we send a lot of messages
>> from le backend domain to the device domain (other way also).
>> Unfortunately, it seems that there is only one S2S output
>> connection establishes between the 2 cluster (i.e. only one of
>> the nodes of the backend cluster establish the connection) and so
>> this is a big bottleneck for us: all the traffic is routed
>> through one host.
>> Is this a limitation of the XMPP protocol, or a limitation of
>> eJabberd ?
>> Is there a way to allow each of our nodes to connect through S2S
>> to another node on the destination cluster ?
> If I understand you correctly, you want s2s connections not to be
> shared across nodes in a cluster. This is not implemented in 2.x,
> but it's the default (and the only) behavior in 3.x.
Yes this is exactly what I'm looking for. Good to ear that 3.x will
handle that. Is there a release date for 3.x ? It has been a long
time since I've eared about this version.
More information about the ejabberd