Mailing-List: contact mapreduce-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-dev@hadoop.apache.org
Date: Sat, 23 Nov 2013 19:07:35 +0000 (UTC)
From: "Gera Shegalov (JIRA)" <jira@apache.org>
To: mapreduce-dev@hadoop.apache.org
Message-ID: <JIRA.12680895.1385233637582.19444.1385233655776@arcas>
In-Reply-To: <JIRA.12680895.1385233637582@arcas>
References: <JIRA.12680895.1385233637582@arcas>
Subject: [jira] [Created] (MAPREDUCE-5648) Allow user-specified diagnostics
 and speculation diagnostics for killed tasks
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Gera Shegalov created MAPREDUCE-5648:
----------------------------------------

             Summary: Allow user-specified diagnostics and speculation diagnostics for killed tasks
                 Key: MAPREDUCE-5648
                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5648
             Project: Hadoop Map/Reduce
          Issue Type: Improvement
          Components: client, mr-am, mrv2
    Affects Versions: 2.2.0
            Reporter: Gera Shegalov


Our users and tools want to be able to supply additional custom diagnostic messages to mapreduce ClientProtocol killTask.

We also need to clearly indicate when a task attempt is killed because another task attempt succeeded first when speculative execution is enabled.


--
This message was sent by Atlassian JIRA
(v6.1#6144)