Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Duplicate
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:
None

Sprint:
Server Serverless 2022-06-27, Server Serverless 2022-08-22
Linked BF Score:
15
Confidence Status:
None
Work Order:
3

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name:
None
Goal Link:
None

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.

is duplicated by

SERVER-67884 Handle lastCommittedOpTime correctly during shard split

Closed

is related to

SERVER-68931 Drain oplog buffers before applying recipient config

Closed

SERVER-68958 Monitor shard split recipient nodes for highest lastApplied

Closed

SERVER-68964 Reset lastCommittedOpTime to blockTimestamp after applying recipient config

Closed

Assignee:: Matt Broadstone
Reporter:: Didier Nadeau
Participants:: Didier Nadeau, Matt Broadstone
Votes:: 0 Vote for this issue
Watchers:: 3 Start watching this issue

Created:: Jun 13 2022 09:05:08 PM UTC
Updated:: Sep 07 2022 09:33:21 PM UTC
Resolved:: Sep 07 2022 09:33:20 PM UTC
Confidence Status Last Update:: 21/Jun/22 2:54 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates