-
Type:
Improvement
-
Resolution: Won't Do
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Sharding EMEA
-
Sharding EMEA 2023-05-29, Sharding EMEA 2023-06-12, Sharding EMEA 2023-06-26, Sharding EMEA 2023-07-10, Sharding EMEA 2023-07-24, Sharding EMEA 2023-08-07, Sharding EMEA 2023-08-21, Sharding EMEA 2023-09-04, Sharding EMEA 2023-09-18
-
3
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
-
None
When all the chunks for a collection have been moved off AND all ongoing reads on orphaned documents have drained, the range-deleter should safely be able to:
- Stop incoming migrations for the collection
- Drop the collection locally
This would help avoid all the unnecessary overhead caused by the range deleter: delete the whole collection/indexes rather than doing it document by document.