[
https://issues.apache.org/jira/browse/ZOOKEEPER-1652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13813565#comment-13813565
]
Camille Fournier commented on ZOOKEEPER-1652:
---------------------------------------------
I believe this addresses the same issue as ZOOKEEPER-1666, but will work for
3.4.6. So I'm going to use this for 3.4.6, but not trunk, which was resolved
with the other patch.
> zookeeper java client does a reverse dns lookup when connecting
> ---------------------------------------------------------------
>
> Key: ZOOKEEPER-1652
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1652
> Project: ZooKeeper
> Issue Type: Bug
> Components: java client
> Affects Versions: 3.4.5
> Reporter: Sean Bridges
> Assignee: Sean Bridges
> Priority: Critical
> Attachments: ZOOKEEPER-1652.patch
>
>
> When connecting to zookeeper, the client does a reverse dns lookup on the
> hostname. In our environment, the reverse dns lookup takes 5 seconds to
> fail, causing zookeeper clients to connect slowly.
> The reverse dns lookup occurs in ClientCnx in the calls to adr.getHostName()
> {code}
> setName(getName().replaceAll("\\(.*\\)",
> "(" + addr.getHostName() + ":" + addr.getPort() + ")"));
> try {
> zooKeeperSaslClient = new
> ZooKeeperSaslClient("zookeeper/"+addr.getHostName());
> } catch (LoginException e) {
> {code}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
