You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-dev@hadoop.apache.org by "Arun C Murthy (JIRA)" <ji...@apache.org> on 2010/03/05 04:43:34 UTC

[jira] Created: (MAPREDUCE-1560) Better diagnostic message for tasks killed for going over vmem limit

Better diagnostic message for tasks killed for going over vmem limit
--------------------------------------------------------------------

                 Key: MAPREDUCE-1560
                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1560
             Project: Hadoop Map/Reduce
          Issue Type: Bug
          Components: tasktracker
            Reporter: Arun C Murthy
            Assignee: Arun C Murthy
             Fix For: 0.22.0


Currently the user has no indication of his tasks getting killed due to vmem limit, the only way to know is by looking at TT logs. We should get the TT to insert a diagnostic string for the task to indicate this.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (MAPREDUCE-1560) Better diagnostic message for tasks killed for going over vmem limit

Posted by "Vinod K V (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/MAPREDUCE-1560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vinod K V resolved MAPREDUCE-1560.
----------------------------------

    Resolution: Invalid

We already have this feature. It is just that because of a bug in the diagnostics framework, we don't always record the information. Head to MAPREDUCE-1563 for the bug in question. Resolving this as invalid.

> Better diagnostic message for tasks killed for going over vmem limit
> --------------------------------------------------------------------
>
>                 Key: MAPREDUCE-1560
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1560
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: tasktracker
>            Reporter: Arun C Murthy
>            Assignee: Arun C Murthy
>             Fix For: 0.22.0
>
>
> Currently the user has no indication of his tasks getting killed due to vmem limit, the only way to know is by looking at TT logs. We should get the TT to insert a diagnostic string for the task to indicate this.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.