-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Sharding
-
Fully Compatible
-
ALL
-
Sharding 2019-01-14, Sharding 2019-01-28
-
0
Right now, if a commit, abort, or prepare message to a transaction participant fails, we retry immediately. It might be worth adding some sort of backoff so that we slow down retries if they keep failing. Same goes for targeting a shard in the coordinator code.
- is duplicated by
-
SERVER-38798 shard registry busy-loops in commitTransaction
- Closed
-
SERVER-38444 Coordinating a transaction should run fully in the ThreadPoolTaskExecutor for sharding tasks
- Closed
-
SERVER-38795 Add test that if coordinator fails to target host in participant shard, coordinator schedules a retry attempt
- Closed
-
SERVER-38881 Use ThreadClient rather than onCreateThread to create Clients for work done by TransactionCoordinatorService
- Closed