--On February 13, 2008 3:14:37 AM +0000 quanah@zimbra.com wrote:

--On February 13, 2008 3:03:46 AM +0000 quanah@zimbra.com wrote:

...

And, with the patch for ITS#5282, all replication stops (probably a good thing).

More specifically, the replica stops accepting any new changes, since it can't proceed on the MODs to a non-existent entry. The master of course continues to accept and record changes, and any non-problematic replicas continue to receive changes.

With a build of 2.3 with the (adjusted) patches from HEAD, it looks like this issue is resolved. I fully sync'd a replica from the master, and after it was done, I did a slapcat of them.

A direct diff shows a lot of entries out of order (because the replica gets them in multiple refresh phases), however, if I sort the two ldif files, and do a diff, I get:

[zimbra@smtp-2 tmp]$ sort slave.ldif >slave.ldif.s [zimbra@smtp-2 tmp]$ sort master.ldif >master.ldif.s [zimbra@smtp-2 tmp]$ diff -u master.ldif.s slave.ldif.s [zimbra@smtp-2 tmp]$

No diff. So I believe this is fixed. Sound correct?

--Quanah

--

Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration