You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Roman Guseinov (JIRA)" <ji...@apache.org> on 2018/01/26 07:45:00 UTC
[jira] [Commented] (IGNITE-7192) JDBC: support FQDN to multiple IPs
during connection establishment
[ https://issues.apache.org/jira/browse/IGNITE-7192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16340659#comment-16340659 ]
Roman Guseinov commented on IGNITE-7192:
----------------------------------------
[~alexey.tank2], please review the PR (https://github.com/apache/ignite/pull/3439):
* Implemented connection to host's IP-addresses one by one.
* Added unit tests.
Thanks.
> 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
>
> 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)