[
https://issues.apache.org/jira/browse/HDFS-4394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell resolved HDFS-4394.
----------------------------------
Resolution: Invalid
Closing as invalid. Sorry for the noise. I didn't realize these tests complete
in mere seconds normally. Something is really off in this dev environment.
> QJM client tests require a bit more time in some environments
> -------------------------------------------------------------
>
> Key: HDFS-4394
> URL: https://issues.apache.org/jira/browse/HDFS-4394
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: namenode, test
> Affects Versions: 3.0.0, 2.0.3-alpha
> Environment: Ubuntu 12.04.1 LTS (GNU/Linux 3.2.0-35-generic x86_64),
> Java(TM) SE Runtime Environment (build 1.6.0_37-b06), Java HotSpot(TM) 64-Bit
> Server VM (build 20.12-b01, mixed mode)
> Reporter: Andrew Purtell
> Priority: Trivial
>
> I see hard timeouts of TestQuorumJournalManager and TestQJMWithFaults locally
> on a dual core laptop. Frequent jstacking shows some minor delay in IPv4
> address<->local hostname resolution. These tests start up new "daemons"
> frequently enough for this to be an issue.
> With the patch applied, these tests pass.
> I've made a few tries at improving the behavior of the resolver: I've of
> course insured the 'hosts' file does not have entries which interfere,
> checked nsswitch.conf sanity, as well as experimented with toggling the
> java.net.preferIPv4 system property, finally reconfigured dnsmasq to serve
> local forward and reverse entries, still need the patch. Perhaps I've
> overlooked another option?
--
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
