-
Type:
Task
-
Resolution: Duplicate
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Catalog and Routing
-
🟩 Routing and Topology
-
None
-
None
-
None
-
None
-
None
-
None
The test compares the result of listShard with the result of getShardMap.
When listShard and getShardMap run against different mongos might report different results.
Specifically, getShardMap is empty.
This is probably due to staleness as getShardMap relies on the shardRegistry
The issue is rare, so you need to repeat the test multiple times to reproduce
The goal of the ticket should be to define whether
- this is an issue
- the test requires modifications to ensure the shard registry is not stale
- this is not an issue but it's fine for the test to run against a pinned mongos (current solution)
- depends on
-
SERVER-116303 Investigate why getShardMap might return a stale topology on multiple mongos-es
-
- Backlog
-
- related to
-
SERVER-116303 Investigate why getShardMap might return a stale topology on multiple mongos-es
-
- Backlog
-