-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
CAR Team To Be Assigned
-
1
-
None
-
3
-
TBD
-
🟥 DDL
-
None
-
None
-
None
-
None
-
None
-
None
PlacementHistoryCleanUpJob does not appear to have any unit test nor jstest. Moreover, the fact that it only does meaningful work when the number of placement history entries gets above a certain threshold, that is hardcoded to a very large number (100k), means that in practice this task is almost certainly never tested.
It is true that ShardingCatalogManager::cleanUpPlacementHistory does have unit tests, but all this code is not covered anywhere.
Â
Â
- is related to
-
SERVER-109887 Consider making PlacementHistoryCleanUpJob frequency and thresholds configurable
-
- Backlog
-
- related to
-
SERVER-86278 Investigate discrepancy between ShardLocal and ShardRemote aggregations
-
- Closed
-