ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Igor Belyakov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-11471) JDBC: Thin driver should start with a random server to connect
Date Wed, 20 Mar 2019 15:55:00 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-11471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16797292#comment-16797292

Igor Belyakov commented on IGNITE-11471:

[~vozerov], In current caseĀ RND changing has an effect, becauseĀ @Before method in the test
replaces IgniteUtils.RND instance before the first access to JdbcThinTcpIo. Therefore, JdbcThinTcpIo.IDX_GEN
will be initialized by using updated IgniteUtils.RND.

Anyway, I agree that it's too tricky solution and exposing IgniteUtils.RND wasn't right.

I've reverted last commit.

> 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
> Need to choose the first server randomly to have a better distribution.

This message was sent by Atlassian JIRA

View raw message