[
https://issues.apache.org/jira/browse/YARN-2019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14734202#comment-14734202
]
Hudson commented on YARN-2019:
------------------------------
FAILURE: Integrated in Hadoop-Hdfs-trunk #2279 (See
[https://builds.apache.org/job/Hadoop-Hdfs-trunk/2279/])
Modify the CHANGES.txt to move YARN-2019 Commit log from branch 2.8 to (xgong:
rev 6a5068970567817af78d6ec2dfe474b09533a8d2)
* hadoop-yarn-project/CHANGES.txt
> 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
> Assignee: Jian He
> Priority: Critical
> Labels: ha
> Fix For: 2.8.0, 2.7.2, 2.6.2
>
> Attachments: YARN-2019.1-wip.patch, YARN-2019.patch, YARN-2019.patch
>
>
> 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.3.4#6332)
