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

remove_newly_added_field_after_finishing_initial_sync.js does not wait until the new configuration has been replicated

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 5.0.3, 5.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • v5.0
    • Repl 2021-06-28, Repl 2021-07-12
    • 28

      remove_newly_added_field_after_finishing_initial_sync.js currently doesn't wait until the new configuration has been replicated, before stepping up a secondary. This can cause the step up command to fail, if the secondary is still processing the reconfiguration.

            Assignee:
            vishnu.kaushik@mongodb.com Vishnu Kaushik
            Reporter:
            vishnu.kaushik@mongodb.com Vishnu Kaushik
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: