You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2018/03/19 08:12:00 UTC
[jira] [Updated] (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:all-tabpanel ]
Vladimir Ozerov updated IGNITE-7029:
------------------------------------
Fix Version/s: 2.5
> 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
> Fix For: 2.5
>
>
> 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)