Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 9.0.0-rc0
Affects Version/s: None
Component/s: None
Labels:
None

Assigned Teams:

Catalog and Routing
Backwards Compatibility:
Fully Compatible
Sprint:
CAR Team 2025-10-27, CAR Team 2025-11-10, CAR Team 2025-11-24, CAR Team 2025-12-08, CAR Team 2025-12-22, CAR Team 2026-01-05, CAR Team 2026-01-19, CAR Team 2026-02-02, CAR Team 2026-05-11
Story Points:
1
CAR Domain/s:

🟥 DDL

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
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 depended on by

SERVER-125768 Complete TODO listed in SERVER-108231

Closed

is duplicated by

SERVER-108231 Add exhaustive test coverage for the PlacementHistoryCleaner periodic job

Closed

is related to

SERVER-109887 Consider making PlacementHistoryCleanUpJob frequency and thresholds configurable

Closed

related to

SERVER-125768 Complete TODO listed in SERVER-108231

Closed

SERVER-86278 Investigate discrepancy between ShardLocal and ShardRemote aggregations

Closed

Assignee:: Paolo Polato
Reporter:: Jordi Serra Torrens
Participants:: Githook User, Jordi Serra Torrens, Paolo Polato
Votes:: 0 Vote for this issue
Watchers:: 3 Start watching this issue

Created:: Aug 27 2025 12:27:59 PM UTC
Updated:: May 07 2026 03:02:07 PM UTC
Resolved:: May 07 2026 02:45:53 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates