hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karthik Kambatla (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-1618) Fix invalid transition from NEW to FINAL_SAVING
Date Wed, 29 Jan 2014 18:02:17 GMT

     [ https://issues.apache.org/jira/browse/YARN-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Karthik Kambatla updated YARN-1618:

    Summary: Fix invalid transition from NEW to FINAL_SAVING  (was: Applications transition
from NEW to FINAL_SAVING, and try to update non-existing entries in the state-store)

> Fix invalid transition from NEW to FINAL_SAVING
> -----------------------------------------------
>                 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-1618-3.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

View raw message