[
https://issues.apache.org/jira/browse/IGNITE-11471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16791475#comment-16791475
]
Ignite TC Bot commented on IGNITE-11471:
----------------------------------------
{panel:title=--> Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform .NET (Long Running){color} [[tests 0 TIMEOUT
|https://ci.ignite.apache.org/viewLog.html?buildId=3297710]]
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3297736&buildTypeId=IgniteTests24Java8_RunAll]
> 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
> Assignee: Igor Belyakov
> Priority: Major
> Labels: newbie
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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)
