-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
Fully Compatible
-
CAR Team 2026-07-06, CAR Team 2026-07-20
-
200
-
None
-
None
-
None
-
None
-
None
-
None
-
None
It is possible for a secondary node in an shard acting as an embedded router to have a stale/not fully populated shard registry. The error is retried, but the filling of the shardRegistry is asynchronous, thus there is a possibility for the shardRegistry not being populated in time. This ticket is to ensure that the shardRegistry is properly populated.
- is depended on by
-
SERVER-129901 Re-enable tests once the ShardRegistry issue gets solved
-
- Closed
-
- related to
-
SERVER-130835 Check if validateShardIds can be moved in the c-tor of MergeCursorsStage
-
- Open
-