[SERVER-52795] Implement the distributed transaction oplog write on resharding donors Created: 11/Nov/20  Updated: 29/Oct/23  Resolved: 23/Dec/20

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

Type: Task Priority: Major - P3
Reporter: Blake Oler Assignee: Lamont Nelson
Resolution: Fixed Votes: 0
Labels: PM-234-M2, PM-234-T-lifecycle
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-53372 Remove reshardingTempInterruptBeforeO... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2020-12-14, Sharding 2020-12-28
Participants:
Story Points: 1

 Description   

After a donor shard transitions to kPreparingToMirror, it should write to the oplog that it is now converting all future writes to distributed transactions. This is so that all recipient shards can read this message. These recipient shards will know that they are done applying by reading this oplog message.

The oplog message should have an o2 field matching reshardFinalOp (bonus points if you pull out that magic string into a global variable), and should look something like this.



 Comments   
Comment by Githook User [ 23/Dec/20 ]

Author:

{'name': 'LaMont Nelson', 'email': 'lamont.nelson@mongodb.com', 'username': 'lamontnelson'}

Message: SERVER-52795 Resharding donors write final oplog entry upon entering the preparing-to-mirror state.
Branch: master
https://github.com/mongodb/mongo/commit/e3372897dcea110233204133a8e62141ba2db70d

Comment by Lamont Nelson [ 22/Dec/20 ]

Code review: https://mongodbcr.appspot.com/752080008/

Generated at Thu Feb 08 05:29:02 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.