hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rohith Sharma K S (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-261) Ability to fail AM attempts
Date Thu, 08 Oct 2015 06:11:27 GMT

    [ https://issues.apache.org/jira/browse/YARN-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14948134#comment-14948134
] 

Rohith Sharma K S commented on YARN-261:
----------------------------------------

Attached the patch fixing review comments. The attached patch does fail attempt. Regarding
killing attempt, I tried initial prototyping it but it takes some time. I would prefer this
to go in and kill attempt take up later in different JIRA if required. 
[~jlowe] The attached patch 0002-YARN-261.patch is the latest one. Kindly review it

> Ability to fail AM attempts
> ---------------------------
>
>                 Key: YARN-261
>                 URL: https://issues.apache.org/jira/browse/YARN-261
>             Project: Hadoop YARN
>          Issue Type: New Feature
>          Components: api
>    Affects Versions: 2.0.3-alpha
>            Reporter: Jason Lowe
>            Assignee: Rohith Sharma K S
>         Attachments: 0001-YARN-261.patch, 0002-YARN-261.patch, YARN-261--n2.patch, YARN-261--n3.patch,
YARN-261--n4.patch, YARN-261--n5.patch, YARN-261--n6.patch, YARN-261--n7.patch, YARN-261.patch
>
>
> It would be nice if clients could ask for an AM attempt to be killed.  This is analogous
to the task attempt kill support provided by MapReduce.
> This feature would be useful in a scenario where AM retries are enabled, the AM supports
recovery, and a particular AM attempt is stuck.  Currently if this occurs the user's only
recourse is to kill the entire application, requiring them to resubmit a new application and
potentially breaking downstream dependent jobs if it's part of a bigger workflow.  Killing
the attempt would allow a new attempt to be started by the RM without killing the entire application,
and if the AM supports recovery it could potentially save a lot of work.  It could also be
useful in workflow scenarios where the failure of the entire application kills the workflow,
but the ability to kill an attempt can keep the workflow going if the subsequent attempt succeeds.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message