[Date Prev][Date Next]
Less aggressive syncrepl ?
- To: email@example.com
- Subject: Less aggressive syncrepl ?
- From: Jorgen Lundman <firstname.lastname@example.org>
- Date: Tue, 02 Mar 2010 12:26:41 +0900
- User-agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-GB; rv:126.96.36.199pre) Gecko/20090908 SeaMonkey/2.0b2
SunOS ldapmaster01.unix 5.10 Generic_127128-11 i86pc i386 i86pc
We currently have 1 master, and about 25 clients hanging off it, using syncrepl.
Today we restarted the master for the first time in quite some time. This was to
add an index we had forgotten. It was only added to the master.
Initially, the master replies very fast to test-ldapsearch.
But it appears that all 25 clients connect within the first 30seconds or so, and
start the syncing process. This appears to take about 30 minutes of
communicating back and forth. (As observed with snoop/tcpdump).
Simple commandline ldapsearch connect, but never replies. I haven't even started
the software that talks to ldapmaster, so it is essentially doing nothing. (Just
checking everything is in sync, there should be no changes).
This seems rather aggressive. I assume my syncrepl is set far too eagerly.
Normally, syncrepl works beautifully, and updates are very fast across the
board. But having hour long no-response from the master after a restart is
Can someone suggest better values for our syncrepl?
checkpoint 128 15
syncprov-checkpoint 100 10
Slaves has: (RID is based on IP's last octet + 256)
checkpoint 128 15
retry="60 10 300 +"
# wait 60s then retry connect 10 times, then wait 300s forever
Jorgen Lundman | <email@example.com>
Unix Administrator | +81 (0)3 -5456-2687 ext 1017 (work)
Shibuya-ku, Tokyo | +81 (0)90-5578-8500 (cell)
Japan | +81 (0)3 -3375-1767 (home)