[
https://issues.apache.org/jira/browse/IGNITE-11471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16793422#comment-16793422
]
Vladimir Ozerov edited comment on IGNITE-11471 at 3/15/19 7:57 AM:
-------------------------------------------------------------------
[~ibelyakov], implementation looks good, but there are no tests confirming that
it works. Please make sure to add a test confirming that connection is
established to specific node. The test should be deterministic, i.e.
reproducible between runs. Just using Random with a seed from current time will
not work. Need to think on how to externalize the seed or random generator
method so that it can be controlled from the test.
was (Author: vozerov):
[~ibelyakov], implementation looks good,but there are no tests confirming that
it works. Please make sure to add a test confirming that connection is
established to specific node. The test should be deterministic, i.e.
reproducible between runs. Just using Random with a seed from current time will
not work. Need to think on how to externalize the seed or random generator
method so that it can be controlled from the test.
> 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)
