[jira] [Commented] (ZOOKEEPER-1652) zookeeper java client does a reverse dns lookup when connecting
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15608599#comment-15608599
]
Flavio Junqueira commented on ZOOKEEPER-1652:
-
Hello there, This issue duplicates ZOOKEEPER-1666, which has been fixed in
3.4.6 and 3.5.0.
> 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.3.4#6332)
[jira] [Commented] (ZOOKEEPER-1652) zookeeper java client does a reverse dns lookup when connecting
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15608585#comment-15608585
]
Miguel Angel Fernandez Diaz commented on ZOOKEEPER-1652:
Hi,
I have a question about this issue, in which version is this resolved? Because
there is no "Fixed version" in this ticket.
Thanks
> 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.3.4#6332)
[jira] [Commented] (ZOOKEEPER-1652) zookeeper java client does a reverse dns lookup when connecting
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14633725#comment-14633725
]
Andrii Rubtsov commented on ZOOKEEPER-1652:
---
I am using 3.4.6 and I still have slow 5 seconds connections.
What about clone ZOOKEEPER-1661? Is it ok that we have this item closed and
clone still open?
Debugging shows that root cause is definitely near code shown in item
description.
Still not sure what exactly causes the problem in my case.
But! As a quick workaround enlisting all ZK nodes in hosts file definitely
helps.
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.3.4#6332)
[jira] [Commented] (ZOOKEEPER-1652) zookeeper java client does a reverse dns lookup when connecting
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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)
[jira] [Commented] (ZOOKEEPER-1652) zookeeper java client does a reverse dns lookup when connecting
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13813570#comment-13813570
]
Camille Fournier commented on ZOOKEEPER-1652:
-
Actually, when I apply this change with the test for ZOOKEEPER-1666, that test
fails. [~georgecao], [~sbridges], want to take a look?
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)
[jira] [Commented] (ZOOKEEPER-1652) zookeeper java client does a reverse dns lookup when connecting
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13813578#comment-13813578
]
Camille Fournier commented on ZOOKEEPER-1652:
-
Elected to make a patch for ZOOKEEPER-1666 that makes that work on 3.4.6.
Please look there for that, and leave comments.
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)
[jira] [Commented] (ZOOKEEPER-1652) zookeeper java client does a reverse dns lookup when connecting
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13793518#comment-13793518
]
Benjamin Reed commented on ZOOKEEPER-1652:
--
+1 nice fix
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)
[jira] [Commented] (ZOOKEEPER-1652) zookeeper java client does a reverse dns lookup when connecting
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13587433#comment-13587433
]
Hadoop QA commented on ZOOKEEPER-1652:
--
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12571025/ZOOKEEPER-1652.patch
against trunk revision 1448007.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
+1 core tests. The patch passed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1410//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1410//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1410//console
This message is automatically generated.
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
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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
