-
Type:
Task
-
Resolution: Done
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
Fully Compatible
-
None
-
3
-
TBD
-
🟩 Routing and Topology
-
None
-
None
-
None
-
None
-
None
-
None
-
0
During SERVER-103699's work, we discovered that, in a transaction, a shard that acts as a router and routes the request to itself will retry upon StaleConifg.
According to SERVER-93430, a shard should never retry a failed command if it's running inside a txn.
We'll introduce a fix under SERVER-105486. However, we should understand the implications of retrying a failed command from a shard within a txn to discard the need for any CA.
- is related to
-
SERVER-93430 Collection and database routers should not retry if shard acted as a sub router
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-