[
https://issues.apache.org/jira/browse/YARN-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13877254#comment-13877254
]
Karthik Kambatla commented on YARN-1618:
----------------------------------------
We ran into this when running an Oozie MR workflow against HA RM in secure
mode. The Oozie launcher never launched due to some other issues (yet to be
figured out). However, this has caused the above transition from NEW to
FINAL_SAVING.
bq. We should not save apps that haven't been accepted by the scheduler.
This makes sense. If those are the semantics, clearly a bug has been introduced
contrary to this. May be, we should fix the bug. However, note that this will
lead to lack of any information on the applications that have not been accepted
by the scheduler.
By allowing a transition to FINAL_SAVING, we do record some information
corresponding to this application available to the user later. So, I do see a
benefit to allowing this transition too..
> ZKRMStateStore fails to handle updates to znodes not yet created
> ----------------------------------------------------------------
>
> 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)
