-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: 9.0.0-rc0
-
Component/s: None
-
Catalog and Routing
-
Fully Compatible
-
v9.0
-
CAR Team 2026-07-20, CAR Team 2026-08-03
-
200
-
🟥 DDL, 🟦 Shard Catalog
-
None
-
None
-
None
-
None
-
None
-
None
checkMetadataConsistency has gotten bigger with shards authoritative. Specifically, we are checking chunk metadata between the CSRS, shards, and the in-memory chunk map - which we did not do before. This is done under a DDL lock, preventing DDLs on the namespace. Also, this might lead to reading a lot more content from the CSRS.
We should do at least the following:
- Build observability in the impact from CMC: lock timing/contention, chunk and collection count, etc
- Offer a flag as a means to not do a full chunk information compare. Continue to do a soft check like the count, version, etc.
- Offer a knob that can dial a ful check on/off - example, if less than 10k chunks, do a full check otherwise only a soft check
- is depended on by
-
COMPASS-10927 Investigate changes in SERVER-131669: Knobs, flags and observability to reduce and measure checkMetadataConsistency's impact
-
- Needs Triage
-
-
-
- Needs Discussion
-
- related to
-
SERVER-133006 DBDirectClient does not restore the readPreference when leaving its scope
-
- Investigating
-
-
SERVER-132799 Observe and propose improvements to FTDC metrics for authoritative shards
-
- Needs Scheduling
-
-
-
- Needs Scheduling
-