You are viewing a plain text version of this content. The canonical link for it is here.

Posted to mapreduce-issues@hadoop.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2014/07/19 01:42:40 UTC

[jira] [Resolved] (MAPREDUCE-162) [mapred] Change TaskMemoryManager to use JvmIDs instead of TaskIDs for memory-tracking.

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

Allen Wittenauer resolved MAPREDUCE-162.
----------------------------------------

    Resolution: Won't Fix

> [mapred] Change TaskMemoryManager to use JvmIDs instead of TaskIDs for memory-tracking.
> ---------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-162
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-162
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>            Reporter: Vinod Kumar Vavilapalli
>
> To monitor tasks, TaskMemoryManager uses taskIDs to find pidFiles of the tasks. HADOOP-249 introduced jvm re-use because of which multiple tasks can run in a single JVM, and so will share the same pid(pidFile). HADOOP-249 works on a new task by creating a symlink to the pid-file of the task that ran first in the same jvm. Also, the process(jvm) is repeatedly added and removed from monitoring when tasks(under same jvm) come and go. The symlinks and the repetitive addition/removal from monitoring can be avoided if TaskMemoryManager uses JvmIDs instead of TaskIDs.



--
This message was sent by Atlassian JIRA
(v6.2#6252)