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