[SERVER-76678] Handle replica set config error in shard split fixture Created: 28/Apr/23  Updated: 29/Oct/23  Resolved: 08/May/23

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

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

Issue Links:
Backports
Depends
Assigned Teams:
Serverless
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v7.0
Sprint: Server Serverless 2023-05-15
Participants:
Linked BF Score: 20

 Description   

When we remove recipient nodes in the shard split fixture we might have an error in `replSetReconfig`. We can retry the reconfig as we use `with_naive_retry` but we do not fetch an updated config from the primary because replSetGetConfig is in a separate retry loop. This can lead a situation we can't escape from (if the config we try to apply is state).

Instead, in case of issue, we need to fetch the new primary, fetch the most recent config and reconfig using it.



 Comments   
Comment by Githook User [ 08/May/23 ]

Author:

{'name': 'Didier Nadeau', 'email': 'didier.nadeau@mongodb.com', 'username': 'nadeaudi'}

Message: SERVER-76678 Handle replica set config error in shard split fixture
Branch: master
https://github.com/mongodb/mongo/commit/6570bf9e8fb766c7a79d10219184a538e1c0cee8

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