[SERVER-45339] Make MigrationSourceManager send _recvChunkStart to recipient shard as a retryable write Created: 02/Jan/20  Updated: 29/Oct/23  Resolved: 04/Feb/20

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

Type: Task Priority: Major - P3
Reporter: Esha Maharishi (Inactive) Assignee: Alexander Taskov (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-38889 Evaluate the usefulness of convert_to... Closed
related to SERVER-46178 ephemeralForTest builder shouldn't ru... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2020-01-27, Sharding 2020-02-10
Participants:

 Description   

The MigrationSourceManager should send _recvChunkStart with an lsid and txnNumber.

_recvChunkStart should be added to the list of commands that can be sent with lsid and txnNumber.

_recvChunkStart should write the pending rangeDeletion entry using the retryable writes machinery. It can check out the session and call TransactionParticipant::beginOrContinue from inside the command body, similar to what the coordinateCommitTransaction command does.

 

This ticket should also make the recipient shard expect _recvChunkStart to be sent as a retryable write if the recipient is in FCV 4.4.



 Comments   
Comment by Githook User [ 04/Feb/20 ]

Author:

{'name': 'Alex Taskov', 'username': 'alextaskov', 'email': 'alex.taskov@mongodb.com'}

Message: SERVER-45339 Make MigrationSourceManager send _recvChunkStart to recipient shard as a retryable write
Branch: master
https://github.com/mongodb/mongo/commit/8d3429fed4e5307a9e79fe99494ccefc388e54f4

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