Red Hat Bugzilla – Bug 819643
Database RUV could mismatch the one in changelog under the stress
Last modified: 2012-06-20 03:15:34 EDT
This bug is created as a clone of upstream ticket: https://fedorahosted.org/389/ticket/359 Found in a stress test. On one master (blademtv5), one RUV (against another master blademtv1) on database stopped being updated, on the other hand, RUV in the changelog keeps updated. The mismatch stops the replication originated on blademtv1. The cause was the simultaneous MODRDN operations caused conflicts and one conflict resolution failed, which left uncommitted CSN in the CSN list in the RUV element. It prevented to get the max CSN to update the RUV on database.
This issue was found executing reliability regression tests. It is blocking QE from executing.
commit d037c6b87607dabf766229bdaf57140a517599af Author: Rich Megginson <rmeggins@redhat.com> Date: Fri May 18 15:49:11 2012 -0600 ssh://pkgs.devel.redhat.com/rpms/389-ds-base
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Cause: Renaming RDN to the same string sequence, in which only upper/lower cases are different in the replicated configuration. Consequence: The rename failed and the corresponding ruv element was untouched in the list. Fix: Allow renaming RDN to the same string with case difference, and make sure the failed ruv element is removed. Result: The heavy renaming operations work with no errors.
mmrepl mmraccept startup 100% (2/2) mmrepl mmraccept run 100% (23/23) mmrepl mmraccept cleanup 100% (1/1) Hence VERIFIED
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2012-0813.html