Dear listmember,
I have a openldap setup consisting of 1 master (read/write) and 4 replica, with around 370.000 entries, ~200 reads/s at the replica and ~5 modifications/s on master.
Replication is just working fine in terms of adding, modify entries, but not, when it comes to deletion of entries.
If I delete an entry at the master, the deletion seems not to be synchronised to the replica. All the replica do have the very same count of objects, but they differ to the masters object count (master have less, because deletions work there...)
What I have found so far is that I only have syncprov_sessionlog configured and the manual page is talking about sessionlog too. Which directive should I use on the syncprov master?
Is there a problem with the delete phase? What else could I check?
Thanks alot in advance!
Best regards, Daniel
On Friday 26 January 2007 11:54, Daniel Eckstein wrote:
Dear listmember,
I have a openldap setup consisting of 1 master (read/write) and 4 replica, with around 370.000 entries, ~200 reads/s at the replica and ~5 modifications/s on master.
Replication is just working fine in terms of adding, modify entries, but not, when it comes to deletion of entries.
If I delete an entry at the master, the deletion seems not to be synchronised to the replica. All the replica do have the very same count of objects, but they differ to the masters object count (master have less, because deletions work there...)
What I have found so far is that I only have syncprov_sessionlog configured and the manual page is talking about sessionlog too. Which directive should I use on the syncprov master?
Is there a problem with the delete phase? What else could I check?
This has been a problem on a few releases in the 2.3 series. You should provide the exact version number you are running ....
Regards, Buchan
Its 2.3.24.
Regards, Daniel
Buchan Milne schrieb:
On Friday 26 January 2007 11:54, Daniel Eckstein wrote:
Dear listmember,
I have a openldap setup consisting of 1 master (read/write) and 4 replica, with around 370.000 entries, ~200 reads/s at the replica and ~5 modifications/s on master.
Replication is just working fine in terms of adding, modify entries, but not, when it comes to deletion of entries.
If I delete an entry at the master, the deletion seems not to be synchronised to the replica. All the replica do have the very same count of objects, but they differ to the masters object count (master have less, because deletions work there...)
What I have found so far is that I only have syncprov_sessionlog configured and the manual page is talking about sessionlog too. Which directive should I use on the syncprov master?
Is there a problem with the delete phase? What else could I check?
This has been a problem on a few releases in the 2.3 series. You should provide the exact version number you are running ....
Regards, Buchan
Upgrade (especially the master) to 2.3.33 and try again.
http://www.openldap.org/software/release/changes.html: Fixed slapo-syncprov DEL propagation bug (ITS#4589) (you've found only one of the 14 sync bugs fixed since 2.3.24...do you really want to sit around with 2.3.24 and wait for the other 13+ to hit you?)
On Fri, 26 Jan 2007, Daniel Eckstein wrote:
Its 2.3.24.
Regards, Daniel
Buchan Milne schrieb:
On Friday 26 January 2007 11:54, Daniel Eckstein wrote:
Dear listmember,
I have a openldap setup consisting of 1 master (read/write) and 4 replica, with around 370.000 entries, ~200 reads/s at the replica and ~5 modifications/s on master.
Replication is just working fine in terms of adding, modify entries, but not, when it comes to deletion of entries.
If I delete an entry at the master, the deletion seems not to be synchronised to the replica. All the replica do have the very same count of objects, but they differ to the masters object count (master have less, because deletions work there...)
What I have found so far is that I only have syncprov_sessionlog configured and the manual page is talking about sessionlog too. Which directive should I use on the syncprov master?
Is there a problem with the delete phase? What else could I check?
This has been a problem on a few releases in the 2.3 series. You should provide the exact version number you are running ....
Regards, Buchan
openldap-software@openldap.org