[Date Prev][Date Next] [Chronological] [Thread] [Top]

RE: achieve server redundancy

To: openldap-software@OpenLDAP.org
Subject: RE: achieve server redundancy
From: Tony Earnshaw <tonye@billy.demon.nl>
Date: Thu, 11 Dec 2003 08:16:09 +0100
In-reply-to: <7DE4EF03D8D61B44B927E4A059B2644C01E5E651@usexmail02.us.trendnet.org>
Organization: Billy
References: <7DE4EF03D8D61B44B927E4A059B2644C01E5E651@usexmail02.us.trendnet.org>

tor, 11.12.2003 kl. 04.14 skrev 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.
> 
> I know windows domain controller works this issue out with DNS pretty well, it would periodically update its records in the DNS and the client actually queries the DNS to get the list of healthy servers before really contacting the server. I don't think this approach is available for openLDAP server and other platforms however I might be wrong.
> 
> More comments?

My 2 eurocents' worth: RedHat Enterprise Server 3 is delivered with
hardware clustering software (2 to 8 servers, if i've understood
correctly) and that's what I'd be looking at first - being a RedHat
person ;)

--Tonni

-- 
mail: billy - at - billy.demon.nl
http://billy.demon.nl

References:
- RE: achieve server redundancy
  - From: <Kent_Wu@trendmicro.com>

Prev by Date: stable?
Next by Date: Strict schema checking examples
Index(es):
- Chronological
- Thread