| Author |
Message |
|
| Guest |
 Posted: Thu Feb 22, 2007 8:06 pm |
 |
|
|
Guest
|
Is there a plan to add a load balancer to ejabberd for external components like the Python gateways?
|
|
|
| Back to top |
|
| Guest |
| Posted: Fri Feb 23, 2007 7:02 am |
|
|
|
Guest
|
Hello Brian,
------- Message original -------
De: Safford, Brian <brian.safford@eds.com>
Envoy |
|
|
| Back to top |
|
| Guest |
| Posted: Fri Feb 23, 2007 1:27 pm |
|
|
|
Guest
|
So I get that version if I use SVN to check it out?
Is documentation included on how the balancing is configured?
Thanks,
Brian
-----Original Message-----
From: ejabberd-bounces@jabber.ru [mailto:ejabberd-bounces@jabber.ru] On Behalf Of Mickael Remond
Sent: Friday, February 23, 2007 2:02 AM
To: ejabberd@jabber.ru
Subject: Re: [ejabberd] Balancer for external components
Hello Brian,
------- Message original -------
De: Safford, Brian <brian.safford@eds.com>
Envoy |
|
|
| Back to top |
|
| Guest |
| Posted: Fri Feb 23, 2007 3:09 pm |
|
|
|
Guest
|
Do I need the domain_balance config lines in the config file for *every* node?
-----Original Message-----
From: ejabberd-bounces@jabber.ru [mailto:ejabberd-bounces@jabber.ru] On Behalf Of Mickael Remond
Sent: Friday, February 23, 2007 2:02 AM
To: ejabberd@jabber.ru
Subject: Re: [ejabberd] Balancer for external components
Hello Brian,
------- Message original -------
De: Safford, Brian <brian.safford@eds.com>
Envoy |
|
|
| Back to top |
|
| Guest |
| Posted: Fri Feb 23, 2007 3:15 pm |
|
|
|
Guest
|
well i think documentation is not clear: if we plug 2 components to cluster (each for different node): do we need make their (components) different names (dns names?) or the same name? like alt-1.component.example.com and alt-2.component.example.com ?
On 2/23/07, Safford, Brian < brian.safford@eds.com (brian.safford@eds.com)> wrote:Quote: Do I need the domain_balance config lines in the config file for *every* node?
-----Original Message-----
From: ejabberd-bounces@jabber.ru (ejabberd-bounces@jabber.ru) [mailto:ejabberd-bounces@jabber.ru (ejabberd-bounces@jabber.ru)] On Behalf Of Mickael Remond
Sent: Friday, February 23, 2007 2:02 AM
To: ejabberd@jabber.ru (ejabberd@jabber.ru)
Subject: Re: [ejabberd] Balancer for external components
Hello Brian,
------- Message original -------
De: Safford, Brian <brian.safford@eds.com (brian.safford@eds.com)>
Envoyé: 22.2.'07, |
|
|
| Back to top |
|
| Guest |
| Posted: Fri Feb 23, 2007 3:38 pm |
|
|
|
Guest
|
Hi,
On Feb 23, 2007, at 3:15 PM, Zbyszek Żółkiewski wrote:
> well i think documentation is not clear: if we plug 2 components to
> cluster (each for different node): do we need make their
> (components) different names (dns names?) or the same name? like
> alt-1.component.example.com and alt-2.component.example.com ?
You only need one name for them all. Use the name you have on your
connection port. And then add {domain_balancing, 'name'}
For example, from SAPO configuration:
{10101, ejabberd_service, [
{access, all},
{hosts, [
"msn.im.sapo.pt"
],
[
{password, "OMG!Hackers!"}
]
}
]},
{domain_balancing, "msn.im.sapo.pt", bare_source}.
{domain_balancing_component_number, "msn.im.sapo.pt", N}.
The last one prevents that a instance that restart from reshuffling
all users. Make sure N is equal to the number of compnents you have
connected.
Best regards,
--
Pedro Melo
Blog: http://www.simplicidade.org/notes/
Jabber ID: melo@simplicidade.org
Use Jabber!
_______________________________________________
ejabberd mailing list
ejabberd@jabber.ru
http://lists.jabber.ru/mailman/listinfo/ejabberd
Post recived from mailinglist |
|
|
| Back to top |
|
| Guest |
| Posted: Fri Feb 23, 2007 3:44 pm |
|
|
|
Guest
|
well, that configuration don't work well for GaduGadu transport. I connect two instances of component to different nodes, and it seams that components very often don't know that user is already logged to component on different node, the problem is even bigger when one node fail - then it seamt that component process is "stuck" on server. Only fix then is to restart all cluster.
My example (with alt-1, alt-2) was because: this way ejabberd (for example mod_proxy) is configured for clustering.
On 2/23/07, Pedro Melo < melo@simplicidade.org (melo@simplicidade.org)> wrote:Quote: Hi,
On Feb 23, 2007, at 3:15 PM, Zbyszek Żółkiewski wrote:
> well i think documentation is not clear: if we plug 2 components to
> cluster (each for different node): do we need make their
> (components) different names (dns names?) or the same name? like
> alt-1.component.example.com and alt-2.component.example.com ?
You only need one name for them all. Use the name you have on your
connection port. And then add {domain_balancing, 'name'}
For example, from SAPO configuration:
{10101, ejabberd_service, [
|
|
|
| Back to top |
|
| Guest |
| Posted: Fri Feb 23, 2007 4:53 pm |
|
|
|
Guest
|
Hi,
On Feb 23, 2007, at 3:43 PM, Zbyszek Żółkiewski wrote:
> well, that configuration don't work well for GaduGadu transport. I
> connect two instances of component to different nodes, and it seams
> that components very often don't know that user is already logged
> to component on different node, the problem is even bigger when one
> node fail - then it seamt that component
The components don't need to know. ejabberd should keep each logged
in user in the same instance.
> process is "stuck" on server. Only fix then is to restart all cluster.
We never experience this at SAPO yet.
Best regards,
--
Pedro Melo
Blog: http://www.simplicidade.org/notes/
Jabber ID: melo@simplicidade.org
Use Jabber!
_______________________________________________
ejabberd mailing list
ejabberd@jabber.ru
http://lists.jabber.ru/mailman/listinfo/ejabberd
Post recived from mailinglist |
|
|
| Back to top |
|
|
|
All times are GMT
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum
|
|
|
Digg It
Del.icio.us
Reddit
Facebook
Stumble Upon
Technorati
