[Date Prev][Date Next]
Bug in replication (ITS#1089)
Full_Name: Heinz Ekker
OS: RedHat Linux 6.2
Submission from: (NULL) (188.8.131.52)
We use a heavy loaded directory for authentication purposes. Changes are made to
a master and the data is replicated to (at the moment) two slaves.
One slave, which is under heavy load, shows strange behaviour:
When one entry is inserted and deleted in a short interval, the insert fails,
although the delete succeeded. The entry in the Reject-Log is 'already exists',
when turning on debugging, we see 'id [num] already in cache'. This does not
happen regularly or with any recognizable pattern. Approximately one of a
hundred entries failes thusly.
It seems that deletions are synchronized with the backend (we use LDBM), but not
with the in-memory cache. Or perhaps this is a thread synchronisation problem.
Our cachesize is increased to:
Although with much lower values, this does happen too. Same whether
'dbcachenowsync' is specified or not.