[
https://issues.apache.org/jira/browse/HADOOP-4202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12645922#action_12645922
]
Chris K Wensel commented on HADOOP-4202:
----------------------------------------
The slow down is within ant, not an IDE.
And yes to compensate, I have reorganized my tests so too many daemon threads
don't get stuck in a particular jvm.
And yes, for now, I want a pristine cluster for every relevant test method, not
just for every TestCase, and I don't want an explosion of TestCase classes just
to provide a test on a variation of a particular theme.
since Cascading allows for very short/concise expression of a data processing
usecase, and is easily parameterized, having lots of tests with minor
variations does not render a huge unwieldy TestCase class. (though one in
particular did recently cross that line, and has been recently beaten back)
And yes, I am accepting patches that clean up my crufty tests. But I would be
happy with threads that listen and die when told to.
> 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.
