forked from dork/tarantool-java
-
Notifications
You must be signed in to change notification settings - Fork 18
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 built-in SocketCahnnelProvider, implementing round-robin between several tarantool instances #37
Comments
|
@sharonovd It is unclear whether it is needed for org.tarantool.TarantoolConnection (basic connector functionality) or java.sql.Connection (JDBC). |
@Totktonada basic |
ztarvos
added a commit
to ztarvos/tarantool-java
that referenced
this issue
Nov 30, 2018
Added socket channel provider implementation that would fail-over to the next configured server in a round-robin fashion. Closes tarantool#37
Totktonada
pushed a commit
that referenced
this issue
Dec 10, 2018
Added socket channel provider implementation that would fail-over to the next configured server in a round-robin fashion. Closes #37
ztarvos
added a commit
to ztarvos/tarantool-java
that referenced
this issue
Dec 12, 2018
Added cluster-ready client implementation that would fail-over to the next configured server in a round-robin fashion. Closes tarantool#37
Totktonada
pushed a commit
that referenced
this issue
Dec 13, 2018
Added cluster-ready client implementation that would fail-over to the next configured server in a round-robin fashion. Closes #37
ztarvos
added a commit
to ztarvos/tarantool-java
that referenced
this issue
Dec 13, 2018
Added cluster-ready client implementation that would fail-over to the next configured server in a round-robin fashion. Closes tarantool#37
Totktonada
pushed a commit
that referenced
this issue
Dec 13, 2018
Added cluster-ready client implementation that would fail-over to the next configured server in a round-robin fashion. Closes #37
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Use-case: tarantool is deployed as a geo-distributed cluster, and when one DC goes down, application must switch to reserve DC with minimal service disruption.
Proposal: add built-in Provider which would take several connection URI's as a config, and would quickly try to establish connection to them in a circle, returning the first succesful one.
Edge-case: if all URIs are unavailable, return error.
Such Provider could be used straight-away in described use-case, and would be also useful as a demo of more advanced connection strategies.
The text was updated successfully, but these errors were encountered: