hadoop-mapreduce-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod K V (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (MAPREDUCE-1560) Better diagnostic message for tasks killed for going over vmem limit
Date Fri, 05 Mar 2010 08:48:27 GMT

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


Mime
View raw message