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

Allow for step downs during reconfig in ReplSetTest initiate

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • 3.4.3, 3.5.4
    • None
    • Replication
    • None
    • Fully Compatible
    • ALL
    • v3.4
    • Repl 2017-03-06
    • 0

    Description

      This occurs because replSetReconfig can sometimes cause the primary to step down and the reconfig in ReplSetTest initiate does not account for this. The reconfig helper is a good example of how to handle reconfigs safely.

      The one concern here is that post-SERVER-20844 we make the assumption that nodes[0] is primary after initiate is called. We should ensure that this guarantee is still met, even if the primary steps down during the reconfig. In 3.4 and 3.6 we can use stepUp to accomplish this, but in 3.2 (if we backport SERVER-20844 that far) we either have to accept rare BFs or step down primaries repeatedly until node 0 is elected.

      Attachments

        Activity

          People

            judah.schvimer@mongodb.com Judah Schvimer
            judah.schvimer@mongodb.com Judah Schvimer
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: