[
https://issues.apache.org/jira/browse/IGNITE-7192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16344740#comment-16344740
]
Taras Ledkov commented on IGNITE-7192:
--------------------------------------
[~guseinov], my comments:
1. Please fix javadoc for: {{JdbcThinTcpIo#getAllAddressesByHost}};
2. Now all connection exceptions are swallowed. Please collect the errors and
provide correct reason for {{SQLException}} in case all address are
inaccessible. e.g. you can use the {{Throwable#addSuppressed}} for it.
> JDBC: support FQDN to multiple IPs during connection establishment
> ------------------------------------------------------------------
>
> Key: IGNITE-7192
> URL: https://issues.apache.org/jira/browse/IGNITE-7192
> Project: Ignite
> Issue Type: Improvement
> Components: jdbc
> Affects Versions: 2.1
> Reporter: Alexey Popov
> Assignee: Roman Guseinov
> Priority: Major
> Labels: pull-request-available
>
> Thin JDBC driver may have FQDN (host name) at a connection string.
> Currently, it resolves this FQDN to one IP and tries to connect to this IP
> only.
> It is better to try to connect to multiple IPs one-by-one if DNS returns
> multiple A-records (FQDN can be resolved to several IPs) until successful
> connection. It could give a simple fallback option for the JDBC thin driver
> users.
> A similar functionality is already implemented in ODBC driver.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
