[SERVER-67884] Handle lastCommittedOpTime correctly during shard split Created: 07/Jul/22  Updated: 04/Aug/22  Resolved: 04/Aug/22

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

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

Issue Links:
Duplicate
duplicates SERVER-67247 Cleanly split recipient nodes from do... Closed
Sprint: Server Serverless 2022-08-08
Participants:

 Description   

Decide whether we need to rollback the lastCommittedOpTime, or whether it's correct for us to allow a stale value between entering the shard split critical section and the first election of the recipient set.



 Comments   
Comment by Didier Nadeau [ 04/Aug/22 ]

This issue will be taken care of as part of the larger clean break fix.

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