[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: |
|
||||||||
| 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: |