dont_read_oplog_hole_on_step_up should wait for new primary after stepUp

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.4.0-rc8, 4.7.0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • v4.4
    • Execution Team 2020-06-15
    • 18
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Instead of stepping-up and immediately asserting the new primary has transitioned, we should replace the assertion with a waitForState that gives the node time to fully-transition.

            Assignee:
            Gregory Wlodarek
            Reporter:
            Louis Williams
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: