hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Douglas (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-4202) TaskTracker never stops cleanup threads, MiniMRCluster becomes unstable
Date Sat, 08 Nov 2008 01:34:44 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-4202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12645932#action_12645932

Chris Douglas commented on HADOOP-4202:

bq. I'm unsure how this changes things unless its some fu to get around ant/junit spawn semantics.

This starts a MiniMRCluster and a MiniDFSCluster for the TestCase, not for each test\* run.
It's sped up several of our tests. Depending on how literally you mean "pristine", TestCase::setUp
and TestCase::tearDown might help you clean up any state left from previous tests, too.

Sorry, I thought these were Hadoop tests that were taking longer. My comments about "correctness"
were scoped to our project and its requirements, only.

> TaskTracker never stops cleanup threads, MiniMRCluster becomes unstable
> -----------------------------------------------------------------------
>                 Key: HADOOP-4202
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4202
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 0.18.1
>            Reporter: Chris K Wensel
>            Assignee: Chris K Wensel
>            Priority: Minor
>         Attachments: hadoop-4202.patch
> If many unit tests start/stop unique MiniMRCluster instances, over time the number of
threads in the test vm grow to large causing tests to hang and/or slow down.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message