[SERVER-68958] Monitor shard split recipient nodes for highest lastApplied Created: 18/Aug/22 Updated: 29/Oct/23 Resolved: 08/Sep/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.2.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Matt Broadstone | Assignee: | Matt Broadstone |
| 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-09-05 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 15 | ||||||||
| Description |
|
The shard split donor should record recipient nodes lastAppliedOpTime as part of its logic for split acceptance. Once all recipient nodes correctly report the recipientSetName, choose the node with the highest lastAppliedOpTime to send the replSetStepUp command to. Additionally, send an appendOplogNote command to the recipient primary after the election, and wait for it to majority commit on the recipient. |