Details
-
Bug
-
Resolution: Fixed
-
Major - P3
-
None
-
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
Description
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.