-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
ALL
-
CAR Team 2024-04-29, CAR Team 2024-05-13
-
200
-
2
A direct connection to a shard could fail with staleConfig after SERVER-80135 since shardCollection information refresh has been converted from sync to async. If a direct connection ends up using stale information, the command fails with the sharding status of collection XYZ Is not currently known and needs to be recovered.
The fix is to not use the direct connection, or do something before to force a refresh.
- related to
-
SERVER-89252 Ban `lookup_targeting.js` to run in `sharding_csrs_continuous_config_stepdown` suite
- Closed
-
SERVER-89548 covered_shardkey_indexes.js test assumes coll metadata is always known on shard
- Closed
-
SERVER-89931 StaleConfig error is not retried as a first statement in a txn with FLE sharded collections
- Closed