[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
RE: achieve server redundancy
- To: openldap-software@OpenLDAP.org
- Subject: RE: achieve server redundancy
- From: "Rick LeMarr" <Rick_LeMarr@hilton.com>
- Date: Thu, 11 Dec 2003 11:42:45 -0600
- Content-class: urn:content-classes:message
- Thread-index: AcO/l93SguqLqcl6QKOi36nK4p58lQAa8oJg
- Thread-topic: achieve server redundancy
> -----Original Message-----
> From: owner-openldap-software@OpenLDAP.org
> [mailto:owner-openldap-software@OpenLDAP.org] On Behalf Of Howard Chu
>
> > From: owner-openldap-software@OpenLDAP.org
> > [mailto:owner-openldap-software@OpenLDAP.org]On Behalf Of
> > Kent_Wu@trendmicro.com
>
> > Round robin sounds good however it still hasn't solved my
> real issue.
> > What I want to achieve is failure-recovery, through Round
> Robin I can
> > achieve a bit load balance however when one server is down, the
> > client who happens to be RR'ed to query that server
> > is going to get an error response still. It seems the load
> > balancing switch might be a good choice since it would
> > probably try to detect the status of those servers.
>
> Yes, go with the load-balancer.
>
Load balancing is not high availability. Two different things with two
different goals.
Has anyone thought of using http://spread.org to achieve high
availability LDAP or an an alternative to the current replication
method? Update anywhere, replicate everywhere.
I think it would be an advantageous abstraction from underlying system
architecture among supporting other benefits like peer-based clustering.
Rick