-
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 has two hardcoded values that define the frequency and thresholds for the cleanup task to execute. We should consider making this configurable through a server parameter, so we can tune them in case they need to be adjusted on a cluster. This would also enable us to reduce them in testing, so we can increase coverage of this functionality.
- related to
-
SERVER-109885 Expand testing of PlacementHistoryCleanUpJob
-
- Backlog
-
-
SERVER-86278 Investigate discrepancy between ShardLocal and ShardRemote aggregations
-
- Closed
-