[I] [Transaction] One single TC unavailable cause transactional throughput down to 0. [pulsar]

[via GitHub]

thetumbled opened a new issue, #23039:
URL: https://github.com/apache/pulsar/issues/23039

   ### 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.
   
![image](https://github.com/user-attachments/assets/97ecfe31-a191-41c7-bbf6-05c544ce7cb4)
   <img width="646" alt="image" 
src="https://github.com/user-attachments/assets/c1ae74f7-49e7-4fa0-9f49-7c3fa8db5072";>
   
   
   ### 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!


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscr...@pulsar.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org