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

Reply via email to