[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: |
|
||||||||||||
| 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: |