-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
ALL
-
200
-
🟩 Routing and Topology
-
None
-
None
-
None
-
None
-
None
-
None
During listCatalog, mongos broadcasts the command to all shards using the shard list from the most recent ShardRegistry refresh. If that list is stale, listCatalog may skip some shards.
Â
To address this, we will force a ShardRegistry refresh within the listCatalog operation before broadcasting the command to all shards.
- is duplicated by
-
SERVER-60746 Client sessions are not causally consistent for sharded metadata
-
- Blocked
-
- is related to
-
SERVER-54979 Calling move/split/mergeChunk after one another from different MongoS is not causally consistent
-
- Closed
-