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

Re: OpenLDAP 2.1 High Availability

To: Kukkala Prasad <kprasad@cordys.com>
Subject: Re: OpenLDAP 2.1 High Availability
From: Michael Ströder <michael@stroeder.com>
Date: Thu, 07 May 2009 14:08:20 +0200
Cc: "openldap-technical@openldap.org" <openldap-technical@openldap.org>
In-reply-to: <E9EE373D35AB4C4A99CCF042C12B6E9A0422E6F69F@ex-ind-u1.vanenburg.com>
References: <E9EE373D35AB4C4A99CCF042C12B6E9A0422E6F0D8@ex-ind-u1.vanenburg.com> <200905071122.51456.bgmilne@staff.telkomsa.net> <E9EE373D35AB4C4A99CCF042C12B6E9A0422E6F69F@ex-ind-u1.vanenburg.com>
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.21) Gecko/20090402 SeaMonkey/1.1.16

Kukkala Prasad wrote:
> Is it safe to upgraded to OpenLDAP 2.4 without testing compatibility/stability of it with our product?

In general it is never safe to upgrade without testing. Upgrading from
2.1 to 2.4 I wouldn't expect too many interop problems with your LDAP
client app though provided you know what you're doing.

But when using multi-master replication you should be aware of some
issues with data consistency when doing load-balancing/automatic
fail-over between the replicas during several write requests.

Worth reading: http://tools.ietf.org/html/draft-zeilenga-ldup-harmful-02

Whether there is any issue with multi-master replication highly depends
on the nature of your data and the behaviour of your application.

Ciao, Michael.

References:
- OpenLDAP 2.1 High Availability
  - From: Kukkala Prasad <kprasad@cordys.com>
- Re: OpenLDAP 2.1 High Availability
  - From: Buchan Milne <bgmilne@staff.telkomsa.net>
- RE: OpenLDAP 2.1 High Availability
  - From: Kukkala Prasad <kprasad@cordys.com>

Prev by Date: RE: OpenLDAP 2.1 High Availability
Next by Date: Re: OpenLDAP 2.1 High Availability
Index(es):
- Chronological
- Thread