[SERVER-51708] submitRangeDeletionTask should handle RangeOverlapConflict error Created: 16/Oct/20  Updated: 29/Oct/23  Resolved: 29/Apr/21

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 4.7.0
Fix Version/s: 5.0.0-rc0

Type: Bug Priority: Major - P3
Reporter: Alexander Taskov (Inactive) Assignee: Janna Golden
Resolution: Fixed Votes: 0
Labels: sharding-csrs-stepdown-also, sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Problem/Incident
Related
related to SERVER-56525 Make thread pool for submitting range... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2020-11-02, Sharding 2020-11-16, Sharding 2020-11-30, Sharding 2020-12-14, Sharding 2020-12-28, Sharding 2021-01-11, Sharding 2021-01-25, Sharding 2021-02-22, Sharding 2021-03-08, Sharding 2021-03-22, Sharding 2021-04-05, Sharding 2021-04-19, Sharding 2021-05-03
Participants:
Linked BF Score: 141

 Description   

The RangeOverlapConflict error is returned from MetadataManager::cleanupRange() but submitRangeDeletionTask ignores it in it's error handler.

The deletion task should be resubmitted if it fails or it should be deleted from config.rangeDeletions if an overlapping range is being submitted.



 Comments   
Comment by Githook User [ 29/Apr/21 ]

Author:

{'name': 'jannaerin', 'email': 'golden.janna@gmail.com', 'username': 'jannaerin'}

Message: SERVER-51708 submitRangeDeletionTask should handle RangeOverlapConflict error
Branch: master
https://github.com/mongodb/mongo/commit/0b829194446f350fe6a8752f651d4b6163e4f62e

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