[
https://issues.apache.org/jira/browse/ZOOKEEPER-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13835250#comment-13835250
]
Jong Wook Kim commented on ZOOKEEPER-1666:
------------------------------------------
Hi, this patch still had the reverse DNS lookup delay issue for me.
I have set connectionString to have hostname (not literal IP), but the stock
3.4.5 client had the delay.
In my case resolvedAddress.toString() also had its hostname as well as the
literal IP, like "hostname/10.0.0.1", apparently not starting with "/".
I guess the if condition should find it already has a resolved IP address
somehow differently.
> 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)
