ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Denis Magda (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-7029) Add an ability to provide multiple connection addresses for thin JDBC driver
Date Tue, 09 Jan 2018 22:31:00 GMT

    [ 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)

Mime
View raw message