hadoop-mapreduce-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Harsh J (Resolved) (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (MAPREDUCE-19) TaskMemoryMonitorThread is not stopped in close
Date Sat, 31 Dec 2011 09:04:30 GMT

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

Harsh J resolved MAPREDUCE-19.

    Resolution: Not A Problem

This hasn't been reported in the recent past, please reopen if its still a problem. Or lets
file a new one if MR2 bases have same issues.
> TaskMemoryMonitorThread is not stopped in close
> -----------------------------------------------
>                 Key: MAPREDUCE-19
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-19
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>            Reporter: Hemanth Yamijala
> The task memory monitor thread is created in initialize, but is not stopped in close.
So, if there's a reinit, this can result in a thread becoming a zombie as the thread variable
is replaced in initialize.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message