hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bikas Saha (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-494) RM should be able to hard stop a lingering app on a NM
Date Fri, 22 Mar 2013 21:39:15 GMT

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

Bikas Saha commented on YARN-494:

Thanks! That makes more sense.
> RM should be able to hard stop a lingering app on a NM
> ------------------------------------------------------
>                 Key: YARN-494
>                 URL: https://issues.apache.org/jira/browse/YARN-494
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: nodemanager, resourcemanager
>    Affects Versions: 0.23.3, 3.0.0, 2.0.0-alpha
>            Reporter: Daryn Sharp
> It's possible for a NM to "leak" applications that the RM believes have finished.  This
currently tends to happen when a lingering app jams in log aggregation or misses the notification
to begin aggregation.
> Until aggregation completes, the NMs send app keepalive requests to the RM so it continues
renewing the app's tokens.  This could be extend to allow the RM to send a hard stop to a
NM for an app that has been running for a configurable interval of time after the app has

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message