[SERVER-69158] Donor waits for majority committed no-op write on recipient primary Created: 25/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

Backwards Compatibility: Fully Compatible
Sprint: Server Serverless 2022-09-05
Participants:

 Description   

The final step of the shard split critical section must wait for a no-op write to majority commit on the recipient primary to prevent invariant rollback of the stable_timestamp on the recipient. If the node selected to be recipient primary goes down after winning an election, another node with a lower lastApplied may win a subsequent election and force the original primary to rollback when it comes back online. Waiting for the selected recipient primary to majority commit a no-op entry while its primary ensures future elections will not cause this rollback.



 Comments   
Comment by Githook User [ 26/Aug/22 ]

Author:

{'name': 'Matt Broadstone', 'email': 'mbroadst@mongodb.com', 'username': 'mbroadst'}

Message: SERVER-69158 Donor waits for majority no-op write on recipient primary
Branch: master
https://github.com/mongodb/mongo/commit/38ae339bc4c352ca8f9a381a7af802468eb0fa8b

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