Wait for majority commit point to be advanced on each node before starting rollback test in rollback_set_fcv.js

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 5.3.0, 5.0.6, 5.2.1, 4.4.13
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • v5.2, v5.1, v5.0, v4.4
    • Replication 2022-01-10
    • 34
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      We should call awaitLastOpCommitted after setting the FCV but before starting the rollback test.

      This is because after setting the FCV, the secondary might not have updated its knowledge of the majority commit point through heartbeats before it is isolated from the set, so its lastFCVUpdateTimestamp will be after the majority commit point, which will cause checking the FCV to hang

              Assignee:
              Huayu Ouyang
              Reporter:
              Huayu Ouyang
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: