You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2013/01/13 21:48:13 UTC

[jira] [Created] (HDFS-4394) QJM client tests require a bit more time in some environments

Andrew Purtell created HDFS-4394:
------------------------------------

             Summary: 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
         Attachments: HDFS-4394.patch

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.IPv4 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