[
https://issues.apache.org/jira/browse/IGNITE-7029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16380214#comment-16380214
]
ASF GitHub Bot commented on IGNITE-7029:
----------------------------------------
GitHub user tledkov-gridgain opened a pull request:
https://github.com/apache/ignite/pull/3585
IGNITE-7029 Add an ability to provide multiple connection addresses for
thin JDBC driver
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-7029
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/3585.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #3585
----
commit bc1efe5f514f576bcd16f009ef2e3b3ffc661487
Author: tledkov-gridgain <tledkov@...>
Date: 2018-02-27T12:48:24Z
IGNITE-7029: add multiple connect addresses
commit 9d17bef8873c935a431d800c7f1beb778d768a09
Author: tledkov-gridgain <tledkov@...>
Date: 2018-02-27T16:22:04Z
Merge branch '_master' into ignite-7029
# Conflicts:
#
modules/core/src/main/java/org/apache/ignite/internal/jdbc/thin/ConnectionPropertiesImpl.java
#
modules/core/src/main/java/org/apache/ignite/internal/jdbc/thin/JdbcThinConnection.java
commit a38ea80419c75473a39c7a9737400c9b36586e0a
Author: tledkov-gridgain <tledkov@...>
Date: 2018-02-28T12:26:43Z
IGNITE-7029: close statements and result sets on disconnect
commit 6e8a548da0585eafaf68904c33b2dff0498f71d9
Author: tledkov-gridgain <tledkov@...>
Date: 2018-02-28T12:26:55Z
Merge branch '_master' into ignite-7029
----
> 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)
