-
Type: Task
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Catalog and Routing
SERVER-96906 has identified an unlikely interleaving that may lead checkMetadataConsistency to report an error during a config server transition.
This ticket aims to explore all potential problematic interactions between checkMetadataConsistency and config transitions (both to and from dedicated). Based on the findings, a decision will be made on whether to implement a specific solution for SERVER-96906 or to adopt a more general, higher-level approach.
- is depended on by
-
SERVER-96906 checkMetadataConsistency can hit tripwire assert while checking shard key index due to local collection dropped mid-check by dedicated config server transition
- Blocked
- related to
-
SERVER-94740 CheckMetadataConsistency can trigger false positives due to looking at sharding metadata while critical section is active
- Closed