[
https://issues.apache.org/jira/browse/ZOOKEEPER-2171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14521796#comment-14521796
]
Raul Gutierrez Segales commented on ZOOKEEPER-2171:
---------------------------------------------------
Hmmm, failed again, thought at a different place:
{noformat}
Error Message
waiting for server 2 being up
Stacktrace
junit.framework.AssertionFailedError: waiting for server 2 being up
at
org.apache.zookeeper.server.quorum.ReconfigRecoveryTest.testCurrentObserverIsParticipantInNewConfig(ReconfigRecoveryTest.java:529)
at
org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:52)
{noformat}
Could this be a bad CI box? Any ideas? cc: [~michim], [~rakeshr]
> avoid reverse lookups in QuorumCnxManager
> -----------------------------------------
>
> Key: ZOOKEEPER-2171
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2171
> Project: ZooKeeper
> Issue Type: Bug
> Components: quorum
> Reporter: Raul Gutierrez Segales
> Assignee: Raul Gutierrez Segales
> Fix For: 3.5.1, 3.6.0
>
> Attachments: ZOOKEEPER-2171.patch, ZOOKEEPER-2171.patch,
> ZOOKEEPER-2171.patch
>
>
> Apparently, ZOOKEEPER-107 (via a quick git-blame look) introduced a bunch of
> getHostName() calls in QCM. Besides the overhead, these can cause problems
> when mixed with failing/mis-configured DNS servers.
> It would be nice to reduce them, if that doesn't affect operational
> correctness.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
