[Date Prev][Date Next]
I dont thing so.
I have found some situations where the contextCSN is the same, but the tree are not synced.
I use a simple script to search all entryCSN from all entries and check then against eachother.
ldapsearch -LLL -b "<BASE CONTEXT>" -x -h <IP1> entryCSN>"$TMPFILE_1.full"
ldapsearch -LLL -b "<BASE CONTEXT>" -x -h <IP2> entryCSN>"$TMPFILE_2.full"
sed -i '1,3 d' "$TMPFILE_1.full"
sed -i '1,3 d' "$TMPFILE_2.full"
more "$TMPFILE_1.full" | grep entryCSN > "$TMPFILE_1.tmp"
more "$TMPFILE_2.full" | grep entryCSN > "$TMPFILE_2.tmp"
sort "$TMPFILE_1.tmp" > "$TMPFILE_1.csn"
sort "$TMPFILE_2.tmp" > "$TMPFILE_2.csn"
diff "$TMPFILE_1.csn" "$TMPFILE_2.csn" > "$TMPFILE_2.diff"
DIFFC1=`cat "$TMPFILE_2.diff" | wc -l`
if [ $DIFFC1 -eq 0 ]; then
On Wed, Jan 21, 2009 at 8:51 PM, Guillaume Arteta <email@example.com>
Sorry for my English google:)
I'm put into production 2 openldap masters, and I asked the same question João Alfredo.
So, if the resultt of this search is the same on all master's this mean that all servers are consistents, right ?
Ok, the ldapsearch (ldapsearch-x-h Master1 ... and ldapsearch-x-h master2 ...)
displays the same values of contextCSN for server ID, but what it
proves that they are synchronized?
The question is, why master node, the ldapsearch ContextCSN displays of 2 servers (001 & 002)
Can be put in place a monitoring system to test the replication by performing 2 ldapsearchs, if even then synchronized values.