ReplSetTest should retry waitForAllNewlyAddedRemovals on NotPrimary errors

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 7.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Replication
    • Fully Compatible
    • ALL
    • Repl 2023-03-20, Repl 2023-04-03, Repl 2023-04-17, Repl 2023-05-01, Repl 2023-05-15, Repl 2023-05-29, Repl 2023-12-11, Repl 2023-12-25
    • 5
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      We are trying to check the config during initiate, but the replica set isn't stable yet and a node starts a priority takeover at the same time. This means that the primary-only parameter (commitmentStatus) we're using when requesting the config causes the command to error with a NotPrimary error.

      We should retry waitForAllNewlyAddedRemovals in that situation.

            Assignee:
            Samyukta Lanka
            Reporter:
            Samyukta Lanka
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: