[Date Prev][Date Next]
A question about Mirror mode sync
- To: firstname.lastname@example.org
- Subject: A question about Mirror mode sync
- From: Andrew Liu <email@example.com>
- Date: Tue, 15 Nov 2011 22:20:44 +0800
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=D01siVZAepNcFF7R16PzLx3vPKPq2jEQT5NazYvxmiA=; b=RuFT8ahD8iS8NPi/1604gagiv0bWPsDHLTZWe0uuA2Nnf/518FI01VR78YFlWkfqBG lqmhdLw0QpCxi0gAs4H0mfXEowAT840ImfiARdxX9kvks/5SKw5AO9gal0vJ1rtEZTsR yr1VvwjPARtJqMdnlzf1aq3/6xPuue/fPbfnM=
I set up two machinesÂ as LDAP server under mirror replication mode using openldap-2.4.26ã
I found aÂ problem: when a server was down,Â any LDAP add operation on the running server will
not propagateÂ immediately to the previous down server after it has restarted,Â but the LDAP delete
Âoperation can do.
Âand I found after 5-10 minutes, the add operation content can be found on the previous down server.
but it seems the time is not constant.
My question: How to enableÂ the add operations content toÂ propagates to the previous down server immediately?
I have ever triedÂ "-c rid=001,sid=001,csn=0 " to force a full load, but didn'tÂ take effect.
I read the OpenLDAP doc, found the session-log doesn't include add operation, what's sync mechanism ofÂ the add operation.