[jira] [Commented] (IGNITE-7029) Add an ability to provide multiple connection addresses for thin JDBC driver
[ 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)
[jira] [Commented] (IGNITE-7029) Add an ability to provide multiple connection addresses for thin JDBC driver
[ https://issues.apache.org/jira/browse/IGNITE-7029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16395315#comment-16395315 ] Taras Ledkov commented on IGNITE-7029: -- [~vozerov], fixed. Please take a look. > 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)
[jira] [Commented] (IGNITE-7029) Add an ability to provide multiple connection addresses for thin JDBC driver
[
https://issues.apache.org/jira/browse/IGNITE-7029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16389621#comment-16389621
]
Vladimir Ozerov commented on IGNITE-7029:
-
[~tledkov-gridgain], my comments:
1) {{ConnectionPropertiesImpl}} - I think it is not good idea to resolve
address on startup. For example, what if user had no connection when
application was started, but then recovered it? Or what if DNS settings were
changed in runtime, so invalid address became valid? We should not force use to
restart his app in this case. My proposal is to call
{{InetAddress.getAllByName}} at *connection time* and then try to connect to
every returned address iteratively.
2) {{JdbcThinSSLUtil.createSSLSocket}} - consequence of p.1, should be fixed as
well
> 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)
[jira] [Commented] (IGNITE-7029) Add an ability to provide multiple connection addresses for thin JDBC driver
[ https://issues.apache.org/jira/browse/IGNITE-7029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16380333#comment-16380333 ] Taras Ledkov commented on IGNITE-7029: -- [~vozerov], [~al.psc], please review the patch. > 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)
[jira] [Commented] (IGNITE-7029) Add an ability to provide multiple connection addresses for thin JDBC driver
[ 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 Date: 2018-02-27T12:48:24Z IGNITE-7029: add multiple connect addresses commit 9d17bef8873c935a431d800c7f1beb778d768a09 Author: tledkov-gridgain 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 Date: 2018-02-28T12:26:43Z IGNITE-7029: close statements and result sets on disconnect commit 6e8a548da0585eafaf68904c33b2dff0498f71d9 Author: tledkov-gridgain 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)
[jira] [Commented] (IGNITE-7029) Add an ability to provide multiple connection addresses for thin JDBC driver
[ https://issues.apache.org/jira/browse/IGNITE-7029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16372779#comment-16372779 ] Taras Ledkov commented on IGNITE-7029: -- [~vozerov] I see at least two ways of the feature implementation: 1. Multiple addresses in connection properties. 2. Gather node addresses from Ignite cluster after connect to any node. Any suggestion? Should we implement load balance on multiple connection ow the first alive address should be used (for the fist implementation)? > 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)
[jira] [Commented] (IGNITE-7029) Add an ability to provide multiple connection addresses for thin JDBC driver
[ https://issues.apache.org/jira/browse/IGNITE-7029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16319593#comment-16319593 ] Khaerul Rizal Damanik commented on IGNITE-7029: --- It will be great if it fixed at 2.4. Hope it can fixed one of my problems. Thanks. > 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 > > 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 (v6.4.14#64029)
[jira] [Commented] (IGNITE-7029) Add an ability to provide multiple connection addresses for thin JDBC driver
[ https://issues.apache.org/jira/browse/IGNITE-7029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16319311#comment-16319311 ] Denis Magda commented on IGNITE-7029: - [~vozerov], could you confirm if the ticket fits into 2.4? Anyway, this should not be a showstopper because this logic can be embedded into an application. If the application loses a connection to one IP address it can re-connect to the cluster via a different one. > 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 > > 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 (v6.4.14#64029)
[jira] [Commented] (IGNITE-7029) Add an ability to provide multiple connection addresses for thin JDBC driver
[ https://issues.apache.org/jira/browse/IGNITE-7029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16318084#comment-16318084 ] Khaerul Rizal Damanik commented on IGNITE-7029: --- How long it will be *Live*? At least tell me the estimated time? Is it will be on 2.4? > 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 > > 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 (v6.4.14#64029)
[jira] [Commented] (IGNITE-7029) Add an ability to provide multiple connection addresses for thin JDBC driver
[ https://issues.apache.org/jira/browse/IGNITE-7029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16269089#comment-16269089 ] Blackfield commented on IGNITE-7029: IGNITE-6942 covers the failover feature. This ticket asks for load balancing feature implemented as well. > 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 >Affects Versions: 2.3 >Reporter: Valentin Kulichenko > > 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 (v6.4.14#64029)
