New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] In Triple protocol , parameter retries does not take effect #14139
Labels
Comments
guipengfei
added
component/need-triage
Need maintainers to triage
type/need-triage
Need maintainers to triage
labels
Apr 28, 2024
This issue has been fixed in 3.2.x, see Revision Number 0f7a62a. It is recommended to upgrade to 3.2.x to fix the problem. Hope it helps you. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Pre-check
Search before asking
Apache Dubbo Component
Java SDK (apache/dubbo)
Dubbo Version
dubbo java 3.1.11,openjdk17
Steps to reproduce this issue
1.消费者端代码,重试次数设置为4,且为tri协议
( For the consumer code, the number of retries is set to 4 and the tri protocol is used )
2. 当接口调用超时时,会报以下错误,发现并未重试
( When an interface call times out, the following error is reported and no retry is found )
( As above, the FailoverClusterInvoker class handles the invocation timeout. Under the tri protocol, the return result from the invokeWithContext(invoker, invocation) is a normal AsyncRpcResult object. Does the retry count fail to take effect as a result of a direct return? )
5.问题:tri协议下,重试次数不生效是bug还是特性,如果是特性,并未看到官方文档的说明
( Problem: Whether the number of retries does not take effect under the tri protocol is a bug or a feature, if it is a feature, it is not described in the official documentation )
What you expected to happen
和dubbo协议一样,消费者端设置额重试次数生效
( As with the dubbo protocol, the number of retries set on the consumer side takes effect )
Anything else
No response
Are you willing to submit a pull request to fix on your own?
Code of Conduct
The text was updated successfully, but these errors were encountered: