Re: Re: N-Way Multi-Master replication - delete problem

[Adrien Futschik <adrien.futschik@atosorigin.com>]

It seems like I am not the only one facing this problem.

Is this officially reported as a bug ?

I found out that when deleting an entry on the master I added it to, it is removed only on this master and deleting is not replicated until I make some other operation on the other master. Seems like the delete is "queued". 

When deleting an entry on the "other" master (not the one I added the entry to), the delete works fine and is correctly replicated. 

Anyone to help me with N-Way Multi-Master replication ?

Adrien Futschik


========================================
 Message date : Jan 07 2009, 06:35 PM
 From : "jakjr" <joao.alfredo@gmail.com>
 To : adrien.futschik@atosorigin.com
 Copy to : 
 Subject : Re: N-Way Multi-Master replication - delete problem
 
 Hello Adrien,
 
 I have the same problem deleting entries on N-Way MultiMaster.
 
 Did you resolved this problem ?
 
 Best Regards.
 
 On Mon, Dec 22, 2008 at 6:10 AM, Adrien Futschik <
 adrien.futschik@atosorigin.com> wrote:
 
 > OK, But then what did I do wrong ? delete an entry shouldn't be a problem
 > with N-Way Multi-Master replication ? should it ?
 >
 > Here is how I have setup-ed my masters :
 >
 > m1 -config :
 > dn: cn=config
 > objectClass: olcGlobal
 > cn: config
 > olcServerID: 1
 >
 > dn: olcDatabase={0}config,cn=config
 > objectClass: olcDatabaseConfig
 > olcDatabase: {0}config
 > olcRootPW:< file://$CONFIGPWF
 >
 > m2 - config :
 > dn: cn=config
 > objectClass: olcGlobal
 > cn: config
 > olcServerID: 2
 >
 > dn: olcDatabase={0}config,cn=config
 > objectClass: olcDatabaseConfig
 > olcDatabase: {0}config
 > olcRootPW:< file://$CONFIGPWF
 >
 > m1 - syncprov :
 > dn: cn=config
 > changetype: modify
 > replace: olcServerID
 > olcServerID: 1 $URI1
 > olcServerID: 2 $URI2
 >
 > dn: olcOverlay=syncprov,olcDatabase={0}config,cn=config
 > changetype: add
 > objectClass: olcOverlayConfig
 > objectClass: olcSyncProvConfig
 > olcOverlay: syncprov
 >
 > dn: olcDatabase={0}config,cn=config
 > changetype: modify
 > add: olcSyncRepl
 > olcSyncRepl: rid=001 provider=$URI1 binddn="cn=config" bindmethod=simple
 >  credentials=$CONFIGPW searchbase="cn=config" type=refreshAndPersist
 >  retry="5 5 300 5" timeout=3
 > olcSyncRepl: rid=002 provider=$URI2 binddn="cn=config" bindmethod=simple
 >  credentials=$CONFIGPW searchbase="cn=config" type=refreshAndPersist
 >  retry="5 5 300 5" timeout=3
 > -
 > add: olcMirrorMode
 > olcMirrorMode: TRUE
 >
 > m2 - syncrepl :
 > dn: olcDatabase={0}config,cn=config
 > changetype: modify
 > add: olcSyncRepl
 > olcSyncRepl: rid=001 provider=$URI1 binddn="cn=config" bindmethod=simple
 >  credentials=$CONFIGPW searchbase="cn=config" type=refreshAndPersist
 >  retry="5 5 300 5" timeout=3
 > olcSyncRepl: rid=002 provider=$URI2 binddn="cn=config" bindmethod=simple
 >  credentials=$CONFIGPW searchbase="cn=config" type=refreshAndPersist
 >  retry="5 5 300 5" timeout=3
 > -
 > add: olcMirrorMode
 > olcMirrorMode: TRUE
 >
 > m1 - schema :
 > include: file://$ABS_SCHEMADIR/core.ldif
 > include: file://$ABS_SCHEMADIR/cosine.ldif
 > include: file://$ABS_SCHEMADIR/inetorgperson.ldif
 > include: file://$ABS_SCHEMADIR/openldap.ldif
 > include: file://$ABS_SCHEMADIR/nis.ldif
 >
 > m1 - backend :
 > dn: olcDatabase={1}$BACKEND,cn=config
 > objectClass: olcDatabaseConfig
 > objectClass: olc${BACKEND}Config
 > olcDatabase: {1}$BACKEND
 > olcSuffix: $BASEDN
 > olcDbDirectory: ./openldap-data
 > olcRootDN: $MANAGERDN
 > olcRootPW: $PASSWD
 > olcSyncRepl: rid=004 provider=$URI1 binddn="$MANAGERDN" bindmethod=simple
 >  credentials=$PASSWD searchbase="$BASEDN" type=refreshOnly
 >  interval=$INTERVAL retry="5 5 300 5" timeout=3
 > olcSyncRepl: rid=005 provider=$URI2 binddn="$MANAGERDN" bindmethod=simple
 >  credentials=$PASSWD searchbase="$BASEDN" type=refreshOnly
 >  interval=$INTERVAL retry="5 5 300 5" timeout=3
 > olcMirrorMode: TRUE
 >
 > dn: olcOverlay=syncprov,olcDatabase={1}${BACKEND},cn=config
 > changetype: add
 > objectClass: olcOverlayConfig
 > objectClass: olcSyncProvConfig
 > olcOverlay: syncprov
 >
 > Did I miss something ?
 > Has anyone tested N-way Multi-master replication & encountered the same
 > problem as me ?
 >
 > Adrien
 >
 > ========================================
 >  Message date : Dec 19 2008, 07:11 PM
 >  From : "Quanah Gibson-Mount" <quanah@zimbra.com>
 >  To : adrien.futschik@atosorigin.com, openldap-technical@openldap.org
 >  Copy to : "Miguel Jinez" <miguel.jinez@gmail.com>
 >  Subject : Re: Re: N-Way Multi-Master replication - delete problem
 >
 >
 >
 >  --On December 19, 2008 9:28:41 AM +0100 Adrien Futschik
 >  <adrien.futschik@atosorigin.com> wrote:
 >
 >  > Hy everyone,
 >  >
 >  > I have just tested the same procedure with OpenLDAP 2.4.13. The problem
 >  > remains the same.
 >  >
 >  > Did I miss something ? Is this supposed to be like this ?
 >  >
 >  > I'm joining the modified script I'm using to setup both masters and the
 >  > LDIF files I'm using to add and remove an entry (+ attributes).
 >  >
 >  > I did not use access-log, is this supposed to work with N-Way
 >  > Multi-Master replication ? I thought it was only used in case of Delta
 >  > Synchronization/Replication.
 >
 >  Correct, delta-syncrepl and MMR are not currently supported together (that
 >  may change in the future).
 >
 >  --Quanah
 >
 >  --
 >
 >  Quanah Gibson-Mount
 >  Principal Software Engineer
 >  Zimbra, Inc
 >  --------------------
 >  Zimbra ::  the leader in open source messaging and collaboration
 >
 >
 >
 >
 > Adrien Futschik
 >