[Date Prev][Date Next]
Multiple LDAP server IPs to ldap_init, server is busy and failover question.
- To: firstname.lastname@example.org
- Subject: Multiple LDAP server IPs to ldap_init, server is busy and failover question.
- From: Jorgen Lundman <email@example.com>
- Date: Mon, 06 Dec 2010 17:54:46 +0900
- Dkim-signature: v=1; a=rsa-sha256; c=simple/simple; d=lundman.net; s=dkim; t=1291625755; bh=KIL/IBe1Mt+x70nHbg+uN2Zd6c8nOwX7rJOd6QylqY8=; h=Message-ID:Date:From:MIME-Version:To:Subject:Content-Type: Content-Transfer-Encoding; b=rf3hg9OxiSkcrUKkJnn/DVat2sc4DJ4u3i4YJUOSun80YNw4RjnatgLcFBKTAfiVT 5ip27WsGD6gCasmk+6a2aaKcsKOi1rxy5FZW8BFHxlUuE1XaC7QhspHKy5Fvc63AnR tTm6QyFHyTCEaNZ6n2UUhCZK0ySD6p7lOh53lYTU=
- User-agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-GB; rv:126.96.36.199) Gecko/20101027 SeaMonkey/2.0.10
Solaris 10 x86 u8
Can I have some clarification on how failover works when using OpenLDAP library
as a client.
If a piece of software is passing multiple space-separated hosts to ldap_init()
(or initialize) calls, but receives "Server is busy" error during a search
request, should the LDAP library not handle that for the caller
automatically/transparently? Ie, switch to next working LDAP server, and perform
Or is it closer to that ldap_init will find the first working IP (the failover
is early in the flow), but if an already started search later fails, it is up to
the software to retry/reconnect? It only guarantees that the initial connection
What is the general practise here?
Jorgen Lundman | <firstname.lastname@example.org>
Unix Administrator | +81 (0)3 -5456-2687 ext 1017 (work)
Shibuya-ku, Tokyo | +81 (0)90-5578-8500 (cell)
Japan | +81 (0)3 -3375-1767 (home)