hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "sandflee (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3668) Long run service shouldn't be killed even if Yarn crashed
Date Sun, 17 May 2015 13:25:59 GMT

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

sandflee commented on YARN-3668:
--------------------------------

If am crashed and reaches am max fail times, applications are killed. If we set am max fail
times to a big one or unlimit am max fail times, RM may have too many AppAttempt to store
in memory and RMStateStore, YARN-3480 could resolve this problem by storing limited appAttempt.

> Long run service shouldn't be killed even if Yarn crashed
> ---------------------------------------------------------
>
>                 Key: YARN-3668
>                 URL: https://issues.apache.org/jira/browse/YARN-3668
>             Project: Hadoop YARN
>          Issue Type: Wish
>            Reporter: sandflee
>
> For long running service, it shouldn't be killed even if all yarn component crashed,
with RM work preserving and NM restart, yarn could take over applications again.



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

Mime
View raw message