hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gera Shegalov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-5648) Allow user-specified diagnostics and speculation diagnostics for killed tasks
Date Sat, 23 Nov 2013 19:15:36 GMT

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

Gera Shegalov updated MAPREDUCE-5648:
-------------------------------------

    Attachment: Screen Shot 2013-11-23 at 11.12.15 AM.png

Job history after 
mapred job -fail-task <taskAttemptID> "a bad reason"
and subsequent speculative execution.

> 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
>            Assignee: Gera Shegalov
>         Attachments: Screen Shot 2013-11-23 at 11.12.15 AM.png
>
>
> 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)

Mime
View raw message