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.

Sign up for GitHub

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

Jump to bottom

Instance load-balancing and retry tracking issue #211

Closed

sosthene-nitrokey opened this issue Aug 23, 2024 · 2 comments

Contributor

sosthene-nitrokey commented Aug 23, 2024 •

edited by jans23

Loading

On retry: force use of a fresh connection #201
Instances are not used in actual round-robin #178
On retry: try another instance #202
- Change instance when attempting a retry #206 -> This still does not adress the case where retry < num_instances
Retries: clarify interaction between retries and instances #209
Implement short retries in single threaded context #223
Request failure: mark instance as "bad" with exponential backoff #210
Retries: count should be the number of retries, not the number of tries. So a count of 1 should lead to 2 connection being attempted #204
See discussion for some more info Rework the connection management #212

The text was updated successfully, but these errors were encountered:

Member

jans23 commented Sep 19, 2024

Can this be closed?

sosthene-nitrokey closed this as completed

Contributor Author

sosthene-nitrokey commented Sep 19, 2024

Yes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment