[SERVER-67417] Prevent donor primary stepdown due to invalid replSetUpdatePosition during shard split Created: 21/Jun/22 Updated: 29/Oct/23 Resolved: 30/Jun/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.1.0-rc0 |
| Type: | Task | 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: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Server Serverless 2022-06-27, Server Serverless 2022-07-11 | ||||
| Participants: | |||||
| Linked BF Score: | 26 | ||||
| Description |
|
Nodes that are separated from the replica set into their own newly-created set during a shard split, called recipient nodes, needs to reset their sync source in a deterministic fashion. This will ensure replSetUpdatePosition commands sent following a shard split will use the correct sync source. |
| Comments |
| Comment by Githook User [ 30/Jun/22 ] |
|
Author: {'name': 'Didier Nadeau', 'email': 'didier.nadeau@mongodb.com', 'username': 'nadeaudi'}Message: |