Mailing-List: contact mapreduce-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-dev@hadoop.apache.org
Message-ID: <839468890.91621267778907383.JavaMail.jira@brutus.apache.org>
Date: Fri, 5 Mar 2010 08:48:27 +0000 (UTC)
From: "Vinod K V (JIRA)" <jira@apache.org>
To: mapreduce-dev@hadoop.apache.org
Subject: [jira] Resolved: (MAPREDUCE-1560) Better diagnostic message for
 tasks killed for going over vmem limit
In-Reply-To: <408258110.88741267760614432.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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