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

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: 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
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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
              Reporter:
              Vishnu Kaushik
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: