[SERVER-74363] ReplSetTest should retry waitForAllNewlyAddedRemovals on NotPrimary errors Created: 24/Feb/23  Updated: 15/Dec/23  Resolved: 15/Dec/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.3.0-rc0

Type: Bug Priority: Major - P3
Reporter: Samyukta Lanka Assignee: Samyukta Lanka
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Assigned Teams:
Replication
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: 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
Participants:
Linked BF Score: 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.



 Comments   
Comment by Githook User [ 15/Dec/23 ]

Author:

{'name': 'Samy Lanka', 'email': 'samy.lanka@mongodb.com', 'username': 'lankas'}

Message: SERVER-74363 ReplSetTest should retry waitForAllNewlyAddedRemovals on NotWritablePrimary errors

GitOrigin-RevId: 524653de89f25e419d5a0aedaad76cb6fc7d7838
Branch: master
https://github.com/mongodb/mongo/commit/8d136ea6f6e31ee3bad528ff928344f12146d9a6

Comment by Kaitlin Mahar [ 26/Oct/23 ]

I'm going to send this back to the backlog, I have a number of cold BF fixes assigned already that  I've made varying amounts of progress on but I have not gotten to work on this one at all.

Generated at Thu Feb 08 06:27:13 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.