yuz10 opened a new issue, #7295: URL: https://github.com/apache/rocketmq/issues/7295
### Before Creating the Enhancement Request - [X] I have confirmed that this should be classified as an enhancement rather than a bug/feature. ### Summary Normally, when one broker group is down, then producer will retry and send message to another broker. Howerver, if no tcp package replied (caused by net work error or machine shutdown), the request will time out. In this case, the producer will not retry next broker. The issue reserves 100ms for each retrial. For example, the total timeout=3000, and retryTimes=3, the first attempt will use timeout=2800ms, and the second and third ttempt will use timeout=100ms. ### Motivation In case of send message timeout, producer will not retry next broker. ### Describe the Solution You'd Like Reserve 100ms for each retrial. For example, the total timeout=3000, and retryTimes=3, the first attempt will use timeout=2800ms, and the second and third ttempt will use timeout=100ms. ### Describe Alternatives You've Considered Add extra 100ms for each retrial. For example, the total timeout=3000, and retryTimes=3, the first attempt will use timeout=3000ms, and the second and third ttempt will use timeout=100ms. ### Additional Context _No response_ -- 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...@rocketmq.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
