[SERVER-14873] Ability to pause background rangeDelete jobs Created: 12/Aug/14 Updated: 06/Dec/22 Resolved: 11/Aug/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 2.4.10, 2.6.3 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Alexander Komyagin | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Sharding
|
||||||||
| Participants: | |||||||||
| Description |
|
Sometimes there is an urgent need to migrate chunks off an overloaded shard(s), while still taking the load. In this case any additional load that might be caused by migration cleanup is highly undesirable. In situations when orphaned documents are [temporarily] bearable, it will be useful to have the ability to [temporarily] pause background rangeDeleter activities on mongod level at least until some chunks are moved away and load has been redistributed. |
| Comments |
| Comment by Kaloian Manassiev [ 11/Aug/17 ] |
|
With the WiredTiger storage engine, the impact of range deletion is much less noticeable and also in 3.6, we are introducing a delay for orphan data deletion in order to allow queries on the secondaries to complete. This delay is configurable as per Because of these changes I am closing this ticket as ''Won't Fix". |