[jira] [Commented] (ZOOKEEPER-1666) Avoid Reverse DNS lookup if the hostname in connection string is literal IP address.

["George Cao (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13836176#comment-13836176 ] 

George Cao commented on ZOOKEEPER-1666:
---------------------------------------

I think this is a normal DNS lookup, but NOT a reverse DNS lookup. [~jongwook], do you have some test cases?

> 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
>    Affects Versions: 3.4.5
>            Reporter: George Cao
>            Assignee: George Cao
>              Labels: patch, test
>             Fix For: 3.4.6, 3.5.0
>
>         Attachments: ZOOKEEPER-1666-34.patch, ZOOKEEPER-1666-34v2.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)