[SERVER-19226] RangeDeleter should stop worker threads in its destructor Created: 30/Jun/15  Updated: 06/Dec/22  Resolved: 20/Apr/17

Status: Closed
Project: Core Server
Component/s: Internal Code
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Andrew Morrow (Inactive) Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-27921 Add 'waitForDelete' functionality to ... Closed
Assigned Teams:
Sharding
Backwards Compatibility: Fully Compatible
Participants:

 Comments   
Comment by Nathan Myers [ 20/Apr/17 ]

Fixed in c192a1b9b1e22 SERVER-27921 New Range Deleter

Comment by Nathan Myers [ 20/Apr/17 ]

CollectionRangeDeleter uses a task executor in ShardingState, with nothing left running when there are no tasks.

Comment by Kaloian Manassiev [ 27/Jan/17 ]

The need for this ticket will go away once the new per-collection RangeDeleter logic is in place.

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