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 kill AM attempts
Date Wed, 16 Sep 2015 12:06:47 GMT

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

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

Updated the rebased patch.. I have verified the patch in cluster and it is working fine..

Some of the change from earlier patches are
# The client API takes only application attempt ID. Earlier patch used to take AttemptId also
as an argument.
# The client CLI api is {{./yarn applicationattempt -fail <Application Attempt ID>}}
# Help message for fail attempt is 
{code}
usage: applicationattempt
 -fail <Application Attempt ID>     Fails application attempt.
{code}
# When fail is called upon on application attempt, this attempt failure is counted for checking
maxAttempt to launch.
# More functionality tests can be added. I will add in next patches.

Kindly review the updated patch

> Ability to kill 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, 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