We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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 REPORT
Currently in SyncSend, retries are only worked when there is a network error, but not for common errors such as Broker busy
res, _err := p.client.InvokeSync(ctx, addr, p.buildSendRequest(mq, msg), 3*time.Second) if _err != nil { err = _err continue } return p.client.ProcessSendResponse(mq.BrokerName, res, resp, msg)
In java SDK, It will retry for broker_busy、servicce not available and so on. And It will select a different broker to retry.
broker_busy
servicce not available
This is very helpful in a multi-Broker cluster, so I think it is necessary to fix this problem.
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
BUG REPORT
Currently in SyncSend, retries are only worked when there is a network error, but not for common errors such as Broker busy
In java SDK, It will retry for
broker_busy
、servicce not available
and so on. And It will select a different broker to retry.This is very helpful in a multi-Broker cluster, so I think it is necessary to fix this problem.
The text was updated successfully, but these errors were encountered: