-
Notifications
You must be signed in to change notification settings - Fork 19
add round robin fail-over for a client #98
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
add round robin fail-over for a client #98
Conversation
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.
Thanks for the patch!
I proposed some fixes on the add-round-robin-reconnect-strategy-fixups
branch and leave some comments below.
There is unclear thing for me: I got failures with your RetryingClient implementation, while it seems this should not happen. I worked it around, but of course it should be investigated further (at least to understand what is going on).
31a3b89
to
17a941a
Compare
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.
The PR looks good to me.
I merged #99 recently and this PR need to be rebased. I made it on the add-round-robin-reconnect-strategy-rebased
branch: resolved trivial conflicts within the rebased commit and added the commit with changes I want you to see (I don't sure whether I did good thing around generics).
Added cluster-ready client implementation that would fail-over to the next configured server in a round-robin fashion. Closes tarantool#37
17a941a
to
cf16d5c
Compare
I only noticed one missing |
Added socket channel provider implementation that
would fail-over to the next configured server in a
round-robin fashion.
Closes #37