Race between auto reconfig and stepUp command in dont_read_oplog_hole_on_step_up.js

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.7.0
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • ALL
    • 0
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The auto reconfig to remove the "newlyAdded" field from the config for the newly added third node (node 2) could interfere with the stepUp command issued to node 1, ending up failing the stepUp with "Not standing for election; processing a configuration change"

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

              Created:
              Updated:
              Resolved: