-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Catalog and Routing
-
Fully Compatible
-
v9.0
-
CAR Team 2026-08-03, CAR Team 2026-08-17
-
200
-
🟦 Shard Catalog
-
None
-
None
-
None
-
None
-
None
-
None
During the transition to dedicated config we're running removeShard command which drops the sharding metadata. However currently it drops them only on the primary, but not on the secondaries, which needs to be fixed in order to make reads on secondaries not return invalid results for the short period of time before shards realise themselves that the metadata has been dropped.
- related to
-
SERVER-133001 Make addShard always install an empty CSS on all nodes
-
- Backlog
-
-
SERVER-132479 Extend checkMetadataConsistency to detect CSR states without a matching durable entry
-
- Closed
-