[
https://issues.apache.org/jira/browse/IGNITE-11471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16783581#comment-16783581
]
Stanislav Lukyanov commented on IGNITE-11471:
---------------------------------------------
Choice of the server was random initially, but it was changed to a JVM-local
round-robin in IGNITE-9704.
Need to use keep the `AtomicLong` for local round-robin, but initialize it with
a random value instead of zero.
> JDBC: Thin driver should start with a random server to connect
> --------------------------------------------------------------
>
> Key: IGNITE-11471
> URL: https://issues.apache.org/jira/browse/IGNITE-11471
> Project: Ignite
> Issue Type: Improvement
> Components: jdbc
> Reporter: Stanislav Lukyanov
> Priority: Major
> Labels: newbie
>
> Thin JDBC driver uses a list of server addresses to connect to. Connections
> created in a single JVM will use round-robin to choose the server to connect,
> yielding a uniform distribution. However, the round-robin always starts from
> the first server in the list. It means that multiple JVMs with the same JDBC
> connection URL and one connection each will all connect to the same server.
> Need to choose the first server randomly to have a better distribution.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
