[
https://issues.apache.org/jira/browse/YARN-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13877599#comment-13877599
]
Karthik Kambatla commented on YARN-1618:
----------------------------------------
>From the transitions in RMAppImpl, it looks like the app transitions from NEW
>to NEW_SAVING on START and stores the app in the store during this transition.
>The event of type START comes from RMAppManager#submitApplication().
Looks like we definitely need to revisit these transitions:
# If we don't want the store to be touched until the app is SUBMITTED/ ACCEPTED
(X), we should probably replace the existing NEW_SAVING state with a
corresponding X_SAVING state, and re-jig the transitions to directly go to
KILLED/FAILED from any of the states before this X_SAVING state.
# Or, we can keep the NEW_SAVING state, and have transitions only to
NEW_SAVING, KILLED, FAILED from NEW. All other transitions should go out from
NEW_SAVING.
I am not particular on either approach, but more in favor of the latter - more
likely to have an entry in the store corresponding to the application for a
user to check outside of the submit path.
[~bikassaha], [~vinodkv], [~jianhe] - any other approaches or thoughts?
> 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)
