rollback_after_enabling_majority_reads.js test should wait for restarted node to be in SECONDARY state before running stepUp command

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.3.1, 4.2.2
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • ALL
    • v4.2
    • Repl 2019-11-04
    • 0
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The rollback_after_enabling_majority_reads.js tries to stepUp a node after restarting it. But even after awaitNodesAgreeOnPrimary, the restarted node could still be in STARTUP2 state. Thus, the subsequent replSetStepUp could fail because "because member is not currently a secondary".

            Assignee:
            Lingzhi Deng
            Reporter:
            Lingzhi Deng
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: