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) Applications transition from NEW to FINAL_SAVING, and try to update non-existing entries in the state-store
Date Tue, 21 Jan 2014 16:47:19 GMT

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

Karthik Kambatla updated YARN-1618:
-----------------------------------

    Summary: Applications transition from NEW to FINAL_SAVING, and try to update non-existing
entries in the state-store  (was: ZKRMStateStore fails to handle updates to znodes not yet
created)

> 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: Critical
>         Attachments: yarn-1618-1.patch
>
>
> 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)

Mime
View raw message