[SERVER-53742] Migration commit tries to wait for range deletion even though the cleanup was interrupted Created: 13/Jan/21  Updated: 29/Oct/23  Resolved: 15/Jan/21

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

Type: Bug Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: Kaloian Manassiev
Resolution: Fixed Votes: 0
Labels: PM-1645-Milestone-1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2021-01-25
Participants:
Linked BF Score: 24

 Description   

Even if the migration commit succeeds, it is still possible that the cleanup tasks might not manage to execute, because the node is stepping down and the migration source manager was interrupted.

In this case we should not attempt to wait for range deletion.



 Comments   
Comment by Githook User [ 13/Jan/21 ]

Author:

{'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}

Message: SERVER-53742 Do not try to waitForDelete if migration cleanup failed
Branch: master
https://github.com/mongodb/mongo/commit/d237b2fce711579fe24ea9c9dc2722604a16bbe1

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