[
https://issues.apache.org/jira/browse/YARN-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13882997#comment-13882997
]
Karthik Kambatla commented on YARN-1618:
----------------------------------------
[~bikassaha], [~vinodkv] - will you be able to take a look at the patch? It
would be nice to include this in 2.3 if possible, thought I wouldn't call it a
blocker for 2.3.
> Applications transition from NEW to FINAL_SAVING, and try to update
> non-existing entries in the state-store
> -----------------------------------------------------------------------------------------------------------
>
> Key: YARN-1618
> URL: https://issues.apache.org/jira/browse/YARN-1618
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: resourcemanager
> Affects Versions: 2.2.0
> Reporter: Karthik Kambatla
> Assignee: Karthik Kambatla
> Priority: Blocker
> Attachments: yarn-1618-1.patch, yarn-1618-2.patch
>
>
> YARN-891 augments the RMStateStore to store information on completed
> applications. In the process, it adds transitions from NEW to FINAL_SAVING.
> This leads to the RM trying to update entries in the state-store that do not
> exist. On ZKRMStateStore, this leads to the RM crashing.
> Previous description:
> ZKRMStateStore fails to handle updates to znodes that don't exist. For
> instance, this can happen when an app transitions from NEW to FINAL_SAVING.
> In these cases, the store should create the missing znode and handle the
> update.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
