[YARN-2019] Retrospect on decision of making RM crashed if any exception throw in ZKRMStateStore

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 2.8.0, 2.7.2, 2.6.2, 3.0.0-alpha1
• Labels: ha
• Hadoop Flags: Reviewed
• Assignee: Jian He
• Reporter: Junping Du
• Created: 03/May/14 00:11
• Updated: 25/Oct/19 20:27
• Resolved: 23/Jul/15 01:02

Description

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.

Issue Links

• is related to: YARN-4118 Newly submitted app maybe stuck at saving state if store operation failure is ignored in ZKRMStateStore
• relates to: YARN-4087 Followup fixes after YARN-2019 regarding RM behavior when state-store error occurs
• relates to: YARN-3607 Allow users to choose between failing the daemons vs failing the apps/containers