[Date Prev][Date Next]
Re: (ITS#7104) refreshOnly syncrepl out of sync during bulk update/delete operations
- To: openldap-its@OpenLDAP.org
- Subject: Re: (ITS#7104) refreshOnly syncrepl out of sync during bulk update/delete operations
- From: firstname.lastname@example.org
- Date: Fri, 16 Dec 2011 15:31:36 GMT
- Auto-submitted: auto-generated (OpenLDAP-ITS)
----- Mail Original -----
De: "Howard Chu" <email@example.com>
EnvoyÃ©: Jeudi 8 DÃ©cembre 2011 22h37:21 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne
Objet: Re: (ITS#7104) refreshOnly syncrepl out of sync during bulk update/delete operations
>> I noticed an issue with "refreshOnly" syncrepl when a large number of records is
>> added, updated and deleted. At the end of synchronization the contextCSN is
>> equal on all servers, but the data is out of synchronization for some deleted
>> records that remains undeleted on consumer/slave servers.
>> Restarting the consumer or forcing a synchronization with "slapd ... -c
>> 'rid=1,csn=0' " does not help.
>This appears to caused by the sessionlog overflowing due to incoming modifies
>that occur after the refresh operation has begun. I would call this a
>misconfigured server, since the sessionlog can only ever be useful if you size
>it large enough to accomodate all of your update traffic.
>I don't have any plans to fix this issue; fix the server configuration.
Thank you for your answer.
I withdrew the "syncprov-sessionlog" parameter and this fixed the data loss issue.