[SERVER-60767] Ensure that the execution of removeShard() does not interfere with the scheduling/execution of range deletion tasks. Created: 18/Oct/21  Updated: 26/Oct/23

Status: Backlog
Project: Core Server
Component/s: None
Affects Version/s: Backlog
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Paolo Polato Assignee: Backlog - Catalog and Routing
Resolution: Unresolved Votes: 0
Labels: oldshardingemea
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-50144 Removing a shard with in-progress mig... Backlog
Assigned Teams:
Catalog and Routing
Participants:

 Description   

It has been observed  (SERVER-60387) that removeShard() may prevent range deletion tasks from being executed when the removed node is the recipient of a chunk being moved and it is being shut down while the migration is completing. This scenario should be avoided.

Evaluate whether it's feasible to drain range deletions and delete all orphans (simply issuing a local dropCollection) when running removeShard.


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