hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris K Wensel (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-4202) TaskTracker never stops cleanup threads, MiniMRCluster becomes unstable
Date Fri, 19 Sep 2008 14:12:44 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-4202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Chris K Wensel updated HADOOP-4202:
-----------------------------------

    Attachment: hadoop-4202.patch

Have updated the daemon threads to check the 'running' state, and if not running, will silently
exit. to do this, a couple threads are now calling poll() instead of take(), with a timeout
of 10 seconds. this value is arbitrary. 

I haven't added a test case to guaranteed the threads are gone as this patch is so MiniMRCluster
behaves a little better. and it looks like lifecycle interfaces will be added in a future
patch. please advise otherwise.

> 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.0
>            Reporter: Chris K Wensel
>            Assignee: Chris K Wensel
>         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.


Mime
View raw message