ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-7029) Add an ability to provide multiple connection addresses for thin JDBC driver
Date Mon, 19 Mar 2018 08:06:00 GMT

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

ASF GitHub Bot commented on IGNITE-7029:
----------------------------------------

Github user asfgit closed the pull request at:

    https://github.com/apache/ignite/pull/3585


> Add an ability to provide multiple connection addresses for thin JDBC driver
> ----------------------------------------------------------------------------
>
>                 Key: IGNITE-7029
>                 URL: https://issues.apache.org/jira/browse/IGNITE-7029
>             Project: Ignite
>          Issue Type: Improvement
>          Components: jdbc, sql
>    Affects Versions: 2.3
>            Reporter: Valentin Kulichenko
>            Assignee: Taras Ledkov
>            Priority: Major
>
> Currently we allow only to provide one address when connecting via thin JDBC driver.
This has to issues:
> * If node driver is connected to goes down, the driver stops working.
> * Driver has to always go though the same node - this is a bottleneck.
> As a simple solution we can allow to provide multiple addresses, like MySQL does for
example: https://dev.mysql.com/doc/connector-j/5.1/en/connector-j-usagenotes-j2ee-concepts-managing-load-balanced-connections.html



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message