[Transaction] One single TC unavailable cause transactional throughput down to 0.
- Dominant language
- Java
- Stars
- 15.3k
- Forks
- 3.8k
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 160
Description
### Search before asking
- [X] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar.
### Motivation
Transaction module introduce multiple(default 16) TC to improve performance.
However, if part of TC fail to recover, the throughput of all transactional client down to 0, though there are some TC able to serve for client.

### Solution
When there are some TC able to provide service, transactional client should seek service from these TC, instead of waiting for failed TC recovery.
### Alternatives
_No response_
### Anything else?
_No response_
### Are you willing to submit a PR?
- [X] I'm willing to submit a PR!
Contributor guide
Research direction
Start by tracing the transaction client's transaction-coordinator selection and recovery behavior, then reproduce the case where one coordinator cannot recover. Done means transactional clients continue receiving service from available coordinators instead of waiting for the failed coordinator.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100