[SERVER-67247] Cleanly split recipient nodes from donor set in a deterministic fashion for shard split Created: 13/Jun/22  Updated: 07/Sep/22  Resolved: 07/Sep/22

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

Type: Task Priority: Major - P3
Reporter: Didier Nadeau Assignee: Matt Broadstone
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Duplicate
is duplicated by SERVER-67884 Handle lastCommittedOpTime correctly ... Closed
Related
is related to SERVER-68931 Drain oplog buffers before applying r... Closed
is related to SERVER-68958 Monitor shard split recipient nodes f... Closed
is related to SERVER-68964 Reset lastCommittedOpTime to blockTim... Closed
Sprint: Server Serverless 2022-06-27, Server Serverless 2022-08-22
Participants:
Linked BF Score: 15

 Description   

Currently in shard split the recipient nodes leave the donor set once they see a recipient config in an hearbeat and apply it. However replication of oplogs and some messages are killed at some point after this, which depends on the node. As this has triggered issues, we need to ensure a clean split at a deterministic point for all nodes.



 Comments   
Comment by Matt Broadstone [ 18/Aug/22 ]

Closing this as it has been superseded by the linked tickets.

Comment by Didier Nadeau [ 21/Jun/22 ]

The reset of the sync target will be done in SERVER-67417.

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