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

Race between auto reconfig and stepUp command in dont_read_oplog_hole_on_step_up.js

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 4.7.0
    • None
    • Replication
    • None
    • Fully Compatible
    • ALL
    • 0

    Description

      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"

      Attachments

        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: