Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-44259

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

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 4.3.1, 4.2.2
    • Replication
    • None
    • Fully Compatible
    • ALL
    • v4.2
    • Repl 2019-11-04
    • 0

    Description

      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".

      Attachments

        Issue Links

          Activity

            People

              lingzhi.deng@mongodb.com Lingzhi Deng
              lingzhi.deng@mongodb.com Lingzhi Deng
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: