Леонид Юрьев wrote:
We got a trouble with 2.4.40 syncrepl in the the multi-master mode.
I think is too complex for analyse, and so not yet testcase is ready.
But I noticed a change in ITS#7904 and the impact of LDAP_BUSY upon syncrepl.
For instance, I assume that in case the LDAP_BUSY returned from
ldap_sync_search(), then a syncrepl-connection would be closed and
Yes, syncrepl will retry on any error, including LDAP_BUSY. The patch for
ITS#7904 only has any effect if (1) the consumer is too slow to keep up with
data being sent by syncprov and (2) the entry where the pause occurred is
deleted before the search resumes. In that case, a consumer in refresh would
have to start all over. Possibly, if it is always too slow, it may never make
Let see around the line 1554 of server/slapd/syncrepl.c and below.
Also, nowadays it is no repeatable read txn-isolation during the
search and transfer data over a network.
Does it influence upon syncrepl or not?
No. "repeatable read" only matters if you actually backtrack and re-read
records you already saw in a given transaction. An LDAP search operation only
reads and returns any entry once.
Could anybody dispel my doubts?
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/