[Date Prev][Date Next]
Re: Unconsumed replog causes slapd to shoot to 100% cpu?
--On Friday, January 23, 2004 9:02 PM -0800 Jeff Leung <email@example.com>
Recently I reported that our slave instances (openldap-2.1.22 over
BerkeleyDB.4.1.25) were occasionally reaching 100% cpu time.
I tried upgrading our test boxes to use openldap-2.1.25 and BerkeleyDB
4.2.52-1 a little bit afterwards. However, we ran into the same problems,
but this time with the masters.
The interesting thing is that this only happened a while after we shut
down the slaves. The resulting unconsumed replogs became huge (several
hundred megs). We thought back about it and noticed that this was
happening to our slaves as well when they hit 100% cpu usage (we have
replication done in two stages, once from the master to slaves, and then
from the slaves to a set of backup slaves).
Does anyone know what the effect of an oversized replog is on a slapd? Is
it possible that if the replog gets big enough, slapd spends too much time
writing new data to the replog to service requests, or some other behavior
that would cause load to shoot up to 100%?
Did you turn off slurpd or something? You can leave slurpd running, even
if its replicas are shut down -- That is the process that clears out the
slapd created replog...
Principal Software Developer
GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html