-
Type:
Bug
-
Status: Done
-
Priority:
Critical
-
Resolution: Fixed
-
Affects Version/s: 6.5.0
-
Fix Version/s: 6.5.0
-
Component/s: replication, upgrade
-
Labels:
-
Flagged:Impediment
-
Epic Link:
-
Story Points:2
Found with rev (00fd47957e5)
We have a split DS-RS topology of 2 DS - 2 RS, installed with 2.6.4 version, with data.
We check replication is working by performing some operations which populate the changelog.
We upgrade servers one by one.
Then we check the changelog and sometimes, the changelog is missing some entries and is not consistent between servers:
Expected: ======== /DJ_REPL_RS1/opendj/bin/ldapsearch -h localhost -p 1398 -D "cn=myself" -w password -b "cn=changelog" --countEntries "(objectclass=*)" ... # Total number of matching entries: 9 Got: === /DJ_REPL_RS1/opendj/bin/ldapsearch -h localhost -p 1412 -D "cn=myself" -w password -b "cn=changelog" --countEntries "(objectclass=*)" ... # Total number of matching entries: 5 /DJ_REPL_RS2/opendj/bin/ldapsearch -h localhost -p 1413 -D "cn=myself" -w password -b "cn=changelog" --countEntries "(objectclass=*)" ... # Total number of matching entries: 9
To reproduce (1 time out of 3 on my laptop...)
./run-pybot.py -n -v -s replication_group3.Upgrade -t Replication_Topology_Split_DS_RS opendj
- depends on
-
OPENDJ-5648 Change number indexing does not work on RS-only
-
- Done
-
- is related to
-
OPENDJ-5678 Revisit fix for "Replication: Changelog not in sync on RS-only when upgrading a split DS-RS topology from 2.6.4"
-
- Dev backlog
-