[jadmin] Highly Available Jabber server

[fulan Peng]

You can set up multiple proxies to proxy different nodes. When one
proxy or one node fails, let the client switch to another proxy. As
long as the conversation are saved, it is not a problem for your
clients to switch to another URL.
I have setup Squid on Windows XP. So you can set up many proxies on
personal computers acting as backups. Or you can find some one like me
to help each other as extra proxies. This way, if you have one node
alive, you will be alive.
But I did not work out how to set JWchat to work on a cluster of ejabberd.

I have another way to keep database alive, that is Sequoia database.
The Sequoia can have many backends, your JDBC can point to multiple
sites. Only one backend is enough to make the application survive. If
you want use Sequoia, you better use Wildfire which is JAVA stuff.

On 10/19/06, Zbyszek Żółkiewski <zbyszek at toliman.pl> wrote:
> http://ejabberd.jabber.ru/cisco-slb
>
>
>
>
> On 10/19/06, Daryl Herzmann < akrherz at gmail.com> wrote:
> > On 10/18/06, fulan Peng < fulanpeng at gmail.com> wrote:
> > > I have setup two ejabberd servers. I have clustered its mnesia
> > > database but I do not know how to configure jwchat on it. Now I set up
> > > a Squid proxy on one of the machine and server as proxy for another
> > > one. You may have a test on it:
> > > https://breakevilaxis.org
> > > https://ddint.org
> >
> > thanks for the email.  I've been reading some more and think I
> > understand the concept of a ejabberd cluster, but there is still the
> > issue of how to make it highly available in case of a cluster node
> > failure.  I see options like:
> >
> > 1.  You have some sort of DNS solution and when a node fails, you
> > remove its IP from round robin DNS.  This seems problematic for
> > periods of downtime while DNS updates.
> >
> > 2.  You have a hardware solution that makes a single internet presence
> > out of real servers in the ejabberd cluster.
> >
> > 3.  You use IPVS with two directors and two real servers. I currently
> > do that very successfully with apache, but I need this chat solution
> > to be deployed at a colo/hoster.
> >
> > It seems most hoster sites do not support IP failover (which IPVS)
> > wants.  And I suspect my budget doesn't match my uptime requirements
> > :)
> >
> > am I missing something obvious?
> > thanks,
> > daryl
> > _______________________________________________
> > JAdmin mailing list
> > JAdmin at jabber.org
> > http://mail.jabber.org/mailman/listinfo/jadmin
> > FAQ: http://www.jabber.org/about/jadminfaq.shtml
> > _______________________________________________
> >
>
>
>
> --
> pozdrawiam,
> Zbyszek Żółkiewski
> _______________________________________________
> JAdmin mailing list
> JAdmin at jabber.org
> http://mail.jabber.org/mailman/listinfo/jadmin
> FAQ: http://www.jabber.org/about/jadminfaq.shtml
> _______________________________________________
>
>
>