-
Notifications
You must be signed in to change notification settings - Fork 70
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
Improve retry semantics #2330
Improve retry semantics #2330
Conversation
You're missing DCO. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add changelog
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It depends on which scenarios we retry, if the connection is not established we can retry until there is a timeout. We do you want to remove it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Which error the user will get?
Is it timeout out or connection failure?
6f07ac8
to
3d06615
Compare
@Yury-Fridlyand change log added |
Signed-off-by: Janhavi Gupta <[email protected]>
Replace google-api-python-client with protobuf Signed-off-by: Raphaël Vinot <[email protected]>
Signed-off-by: ort-bot <[email protected]>
* Go: Handling generic arrays instead of only string arrays Signed-off-by: Janhavi Gupta <[email protected]>
…tandalone. (#2303) * Go:Implement generic map handler and config get,set for standalone. Signed-off-by: Janhavi Gupta <[email protected]>
3d06615
to
2f64b79
Compare
a. Absence of command retry configuration in client creation params making retry mechanics unexpected, confusing and inconsistent with command timeout constrains. b. Retry semantics are inconsistent between the CME and CMD client since CMD lacks the retry logic Signed-off-by: ikolomi <[email protected]>
2f64b79
to
70a9065
Compare
a. Absence of command retry configuration in client creation params making retry mechanics unexpected, confusing and
inconsistent with command timeout constrains.
b. Retry semantics are inconsistent between the CME and CMD client since CMD lacks the retry logic
Issue: #2251