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 "Jian He (JIRA)" <ji...@apache.org> on 2015/09/04 00:18:46 UTC
[jira] [Commented] (YARN-4087) Followup fixes after YARN-2019
regarding RM behavior when state-store error occurs
[ https://issues.apache.org/jira/browse/YARN-4087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14729905#comment-14729905 ]
Jian He commented on YARN-4087:
-------------------------------
Right, we should make sure the state is correct if the error is ignored.
Uploaded a new patch which addressed Vinod's comment about the inconsistent state.
Also updated the description about the fixes included in this jira.
> Followup fixes after YARN-2019 regarding RM behavior when state-store error occurs
> ----------------------------------------------------------------------------------
>
> Key: YARN-4087
> URL: https://issues.apache.org/jira/browse/YARN-4087
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Jian He
> Assignee: Jian He
> Attachments: YARN-4087.1.patch, YARN-4087.2.patch, YARN-4087.3.patch
>
>
> Several fixes:
> 1. Set YARN_FAIL_FAST to be false by default, since this makes more sense in production environment.
> 2. Fixes state-store to also notify app/attempt if state-store error is ignored so that app/attempt is not stuck at *_SAVING state
> 3. If HA is enabled and if there's any state-store error, after the retry operation failed, we always transition RM to standby state. Otherwise, we may see two active RMs running. YARN-4107 is one example.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)