-
Type: Bug
-
Resolution: Won't Fix
-
Priority: Major - P3
-
None
-
Affects Version/s: 6.0.0-rc0
-
Component/s: None
-
Catalog and Routing
-
Sharding EMEA 2023-09-18, Sharding EMEA 2023-10-02, Sharding EMEA 2023-10-16, Sharding EMEA 2023-10-30, CAR Team 2023-11-13, CAR Team 2023-11-27, CAR Team 2023-12-11, CAR Team 2023-12-25, CAR Team 2024-01-08, CAR Team 2024-01-22, CAR Team 2024-02-05, CAR Team 2024-02-19, CAR Team 2024-03-04, CAR Team 2024-10-28
-
3
Between the moment a rename collection participant snapshots range deletion task documents and the moment they are restored, the range-deleter could potentially process some deletions.
If that happens, it would mean that:
- The count of orphaned documents for the target collection on disk after the rename may be off for a while
- The BalancerStatsRegistry may track wrong statistics for a while
PS: "a while" means until existing range deletions are drained.
- depends on
-
SERVER-65540 Build range deleter service
- Closed