Ensure there is an opportunity to send a retry message when broker no response #9137
+21
−2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
… response
Which Issue(s) This PR Fixes
Fixes #8997
Brief Description
当broker处于半死不活的状态时（gc，os内存不足等等原因），此时表现无法及时响应客户端的请求。
针对客户端同步发送消息，默认是带有重试策略的。可是此种情况下，客户端可能并没有重试的机会。
详见分析。
How Did You Test This Change?
新增的参数sendMsgMaxTimeoutPerRequest，默认情况下不会影响现有的重试逻辑。
模拟broker暂停的情况，并针对各种情况进行了测试，情况如下：