[
https://issues.apache.org/jira/browse/HADOOP-4202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Douglas updated HADOOP-4202:
----------------------------------
Status: Open (was: Patch Available)
This seems like the wrong fix for two reasons.
# Changing the worker threads to poll at an arbitrary duration solely to
accommodate the unit tests is the wrong tradeoff.
# The default junit policy (also explicitly specified in build.xml) spawns a
new JVM for each TestCase, so it's unclear to me why this should even be an
issue. If a TestCase is creating a new MiniMRCluster for each test, then- in
almost all cases- it is using it incorrectly and the TestCase should be
rewritten.
Have I misunderstood the problem? Is this a regression? Is it still an issue?
Hudson doesn't seem to be running any slower...
> 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.
