zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ZOOKEEPER-1666) Avoid Reverse DNS lookup if the hostname in connection string is literal IP address.
Date Tue, 05 Nov 2013 05:03:17 GMT

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

Hadoop QA commented on ZOOKEEPER-1666:

-1 overall.  Here are the results of testing the latest attachment 
  against trunk revision 1538853.

    +1 @author.  The patch does not contain any @author tags.

    +1 tests included.  The patch appears to include 3 new or modified tests.

    -1 patch.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1743//console

This message is automatically generated.

> 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

View raw message