[SERVER-45744] Migration coordinator recovery task should bump the txnNumber on the session used to send _recvChunkStart Created: 24/Jan/20 Updated: 29/Oct/23 Resolved: 20/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-02-10, Sharding 2020-02-24 | ||||
| Participants: | |||||
| Linked BF Score: | 43 | ||||
| Description |
|
While working on It is to prevent an old donor primary from sending _recvChunkStart after the new donor primary has already completed the recovery, because this would cause a new range deletion task to be written on the recipient that would never get cleaned up. This ticket should make the donor persist the lsid and txnNumber used to send _recvChunkStart again, and make the recovery task do a dummy write using the lsid and txnNumber + 1 on the recipient before sending the decision to the recipient. |
| Comments |
| Comment by Githook User [ 20/Feb/20 ] |
|
Author: {'username': 'alextaskov', 'name': 'Alex Taskov', 'email': 'alex.taskov@mongodb.com'}Message: create mode 100644 jstests/sharding/bump_transaction_prevents_extra_deletion_task_write.js |