You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Camille Fournier (JIRA)" <ji...@apache.org> on 2013/11/05 03:34:17 UTC
[jira] [Updated] (ZOOKEEPER-1666) Avoid Reverse DNS lookup if the
hostname in connection string is literal IP address.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Camille Fournier updated ZOOKEEPER-1666:
----------------------------------------
Attachment: ZOOKEEPER-1666-34.patch
3.4.6 patch
> Avoid Reverse DNS lookup if the hostname in connection string is literal IP address.
> ------------------------------------------------------------------------------------
>
> Key: ZOOKEEPER-1666
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1666
> Project: ZooKeeper
> Issue Type: Improvement
> Components: java client
> Reporter: George Cao
> Assignee: George Cao
> Labels: patch, test
> Attachments: ZOOKEEPER-1666-34.patch, ZOOKEEPER-1666.patch, ZOOKEEPER-1666.patch
>
>
> In our ENV, if the InetSocketAddress.getHostName() is called and the host name in the connection string are literal IP address, then the call will trigger a reverse DNS lookup which is very slow.
> And in this situation, the host name can simply set as the IP without causing any problem.
--
This message was sent by Atlassian JIRA
(v6.1#6144)