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

Audit internal uses of force reconfig and consider using safe reconfig

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 5.0.0-rc0
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • Repl 2021-03-22, Repl 2021-04-05

      When using force reconfig, we will bypass the noop write while also clearing the committed snapshot.

      Previously, internal users of doReplSetReconfig only changed the config term and version (stepup, upgrade/downgrade). We probably favored force reconfigs in these scenarios because they are faster and still safe. Since the content of the config did not change, and therefore did not affect the quorum condition, we did not drop snapshots.

      However, in SERVER-50423, we explicitly rename the slaveDelay field to secondaryDelaySecs, so this check will treat that rename as a content change.

            Assignee:
            jason.chan@mongodb.com Jason Chan
            Reporter:
            pavithra.vetriselvan@mongodb.com Pavithra Vetriselvan
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: