hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod K V (JIRA)" <j...@apache.org>
Subject [jira] Updated: (MAPREDUCE-144) TaskMemoryManager should log process-tree's status while killing tasks.
Date Thu, 03 Sep 2009 13:11:01 GMT

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

Vinod K V updated MAPREDUCE-144:
--------------------------------

    Attachment: MAPREDUCE-144-20090903.txt

Attaching patch.
bq. Firstly, it appears cmdline could be empty if the whole process is swapped out. I suppose
this is possible. Is the method we use reliable then?
We don't have any other simple way of determining the complete command line. Presumably, we
can read it from the process's image on the disk, but the effort is not worth it. Printing
N/A when we find the cmdline empty.

bq. I think getCmdLine can return "Unknown" rather than empty when it can't find a command
line.
Printing N/A here too.

Incorporated the rest of the comments too.

In sum, the dump looks like
{noformat}
        |- PID PPID PGRPID SESSID CMD_NAME VMEM_USAGE(BYTES) FULL_CMD_LINE
        |- 100 1 100 100 (proc1) 100000 proc1 arg1 arg2
        |- 200 100 100 100 (proc2) 200000 proc2 arg3 arg4
        |- 500 400 100 100 (proc5) 400000 proc5 arg9 arg10
        |- 400 200 100 100 (proc4) 400000 proc4 arg7 arg8
        |- 300 200 100 100 (proc3) 300000 proc3 arg5 arg6
{noformat}


> TaskMemoryManager should log process-tree's status while killing tasks.
> -----------------------------------------------------------------------
>
>                 Key: MAPREDUCE-144
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-144
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>            Reporter: Vinod K V
>            Assignee: Vinod K V
>         Attachments: HADOOP-5570-1.patch, HADOOP-5570-20090614.txt, HADOOP-5570-20090615.txt,
HADOOP-5570-20090619.txt, HADOOP-5570-20090622.txt, MAPREDUCE-144-20090902.txt, MAPREDUCE-144-20090903.txt
>
>
> This helps a lot in debugging why a particular task has gone beyond memory limits.

-- 
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