You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Bikas Saha (JIRA)" <ji...@apache.org> on 2014/05/04 19:40:15 UTC
[jira] [Commented] (YARN-2019) Retrospect on decision of making RM
crashed if any exception throw in ZKRMStateStore
[ https://issues.apache.org/jira/browse/YARN-2019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13989059#comment-13989059 ]
Bikas Saha commented on YARN-2019:
----------------------------------
That was the initial code since there was no HA states then. With HA states, the RM should move into standby state upon store error.
> Retrospect on decision of making RM crashed if any exception throw in ZKRMStateStore
> ------------------------------------------------------------------------------------
>
> Key: YARN-2019
> URL: https://issues.apache.org/jira/browse/YARN-2019
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Junping Du
> Priority: Critical
> Labels: ha
>
> Currently, if any abnormal happens in ZKRMStateStore, it will throw a fetal exception to crash RM down. As shown in YARN-1924, it could due to RM HA internal bug itself, but not fatal exception. We should retrospect some decision here as HA feature is designed to protect key component but not disturb it.
--
This message was sent by Atlassian JIRA
(v6.2#6252)