Replicated cluster reindexing and log level

I actually have two separate questions, both aimed at performance tuning my database. The first is about running slapindex on individual cluster members to preserve high availability. Namely, if each cluster member is brought offline individually for reindexing (as opposed to putting them all

understanding replication

I'm a little puzzled by the openldap replication docs; in particular rid, entryuuid, entrycsn, contextcsn fields that I see referenced a lot. I'm guessing the rid is a random chosen id number for the secondary server (consumer?) that is used to compare the master db (entryuuid?) for context?

Less aggressive syncrepl ?

Hello list, openldap-2.3.41 db-4.2.52.NC-PLUS_5_PATCHES SunOS ldapmaster01.unix 5.10 Generic_127128-11 i86pc i386 i86pc We currently have 1 master, and about 25 clients hanging off it, using syncrepl. Today we restarted the master for the first time in quite some time. This was to add an

using translucent proxy as syncrepl provider?

Hi, I'm running openldap-2.4.21 and like to use a translucent proxy as syncrepl provider. My translucent proxy starts without complaining and runs. And the syncprov consumer also did not complain about anything, but it did start to sync. My config is very simple and syncrepl runs wihtout the

Re: understanding replication

On Mon, 1 Mar 2010, Alan Batie wrote: I'm a little puzzled by the openldap replication docs; in particular rid, entryuuid, entrycsn, contextcsn fields that I see referenced a lot. [...] Basically, I'd like to understand the replication process at a slightly higher level than

Re: Less aggressive syncrepl ?

Hello list, openldap-2.3.41 db-4.2.52.NC-PLUS_5_PATCHES SunOS ldapmaster01.unix 5.10 Generic_127128-11 i86pc i386 i86pc We currently have 1 master, and about 25 clients hanging off it, using syncrepl. Today we restarted the master for the first time in quite some time. This was to add

Re: understanding replication

--On Tuesday, March 02, 2010 1:49 PM -0500 Aaron Richton rich...@nbcs.rutgers.edu wrote: I'm guessing the rid is a random chosen id number for the secondary server (consumer?) that is used to compare the master db (entryuuid?) for context? information that indicates sync state? rid is chosen

Re: understanding replication

Aaron Richton wrote: On Mon, 1 Mar 2010, Alan Batie wrote: I'm a little puzzled by the openldap replication docs; in particular rid, entryuuid, entrycsn, contextcsn fields that I see referenced a lot. [...] Basically, I'd like to understand the replication process at a slightly higher level

Re: Less aggressive syncrepl ?

--On Tuesday, March 02, 2010 7:58 PM +0100 masar...@aero.polimi.it wrote: 25 consumers doing a full refresh probably ate up all threads available on the producer. You should either cascade your consumers (build a replication chain where a layer of consumers acts as producers for the

Mirrormode Docs

Hi, to my understanding the admin guide on mirrormode is misleading. http://www.openldap.org/doc/admin24/replication.html#MirrorMode According to this documentation both nodes have to be put into mirror mode, as far as I understand the concept of mirror mode, and is described in slapd.conf(5),

Re: Mirrormode Docs

Dieter Kluenter wrote: Hi, to my understanding the admin guide on mirrormode is misleading. http://www.openldap.org/doc/admin24/replication.html#MirrorMode According to this documentation both nodes have to be put into mirror mode, as far as I understand the concept of mirror mode, and is