Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 8.1.0-rc0
Affects Version/s: None
Component/s: None
Labels:
None

Assigned Teams:

Cluster Scalability
Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Sprint:
Cluster Scalability 2024-08-19, Cluster Scalability 2024-09-02
Linked BF Score:
0
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

Sub routers by design are not allowed to retry on any errors. Doing so can result in bugs like the one we see in BF-34353.

is related to

SERVER-101255 Unify stale exception retry handlers in TransactionRouter

Open

related to

SERVER-105486 Collection and database routers should not retry if shard is a txn participant

Closed

SERVER-105723 Investigate the implications of a shard retrying a failed command in a transaction

Closed

Assignee:: Wenqin Ye
Reporter:: Wenqin Ye
Participants:: Githook User, Wenqin Ye
Votes:: 0 Vote for this issue
Watchers:: 5 Start watching this issue

Created:: Aug 09 2024 03:38:32 PM UTC
Updated:: May 30 2025 09:22:30 AM UTC
Resolved:: Sep 09 2024 09:43:56 PM UTC
Confidence Status Last Update:: 12/Aug/24 1:58 PM