-
Type:
Bug
-
Resolution: Won't Fix
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Catalog and Routing
-
v9.0
-
CAR Team 2026-06-08, CAR Team 2026-08-03
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Temporary resharding collections undergo various changes in the sharding catalog without taking any critical section on it. The expectation is that no user should be accessing it and trigger a filtering metadata refresh/recovery which would in turn cause checkMetadataConsistency to fail.
This ticket is about exempting those collections explicitly in checkMetadataConsistency calls unless the user directly asks for a check on the collection itself.
- is related to
-
SERVER-132481 Quiesced resharding operations can cause conflicts during retries of ongoing operations
-
- Closed
-