zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Camille Fournier (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ZOOKEEPER-1666) Avoid Reverse DNS lookup if the hostname in connection string is literal IP address.
Date Wed, 13 Nov 2013 14:17:22 GMT

     [ https://issues.apache.org/jira/browse/ZOOKEEPER-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Camille Fournier updated ZOOKEEPER-1666:
----------------------------------------

    Affects Version/s: 3.4.5
        Fix Version/s: 3.5.0
                       3.4.6

> 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)

Mime
View raw message