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

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.3.1, 4.2.2
    • Component/s: Replication
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v4.2
    • Sprint:
      Repl 2019-11-04
    • Linked BF Score:
      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

          causes

          Bug - A problem which impairs or prevents the functions of the product. SERVER-44643 Use awaitSecondaryNodes in rollback_after_enabling_majority_reads.js instead of waitForState

          • Major - P3 - Major loss of function.
          • Closed

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: