You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Yesha Vora (JIRA)" <ji...@apache.org> on 2016/08/05 22:20:20 UTC
[jira] [Updated] (YARN-5477) ApplicationId should not be visible to
client before NEW_SAVING state
[ https://issues.apache.org/jira/browse/YARN-5477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yesha Vora updated YARN-5477:
-----------------------------
Description:
we should not return applicationId to client before entering NEW_SAVING state.
As per design, RM restart/failover is not supported when application is in NEW state. Thus, It makes sense to return appId to client after entering to NEW_SAVING state.
was:
we should not return application to client before entering NEW_SAVING state.
As per design, RM restart/failover is not supported when application is in NEW state. Thus, It makes sense to return appId to client after entering to NEW_SAVING state.
> ApplicationId should not be visible to client before NEW_SAVING state
> ---------------------------------------------------------------------
>
> Key: YARN-5477
> URL: https://issues.apache.org/jira/browse/YARN-5477
> Project: Hadoop YARN
> Issue Type: Bug
> Components: yarn
> Reporter: Yesha Vora
> Priority: Critical
>
> we should not return applicationId to client before entering NEW_SAVING state.
> As per design, RM restart/failover is not supported when application is in NEW state. Thus, It makes sense to return appId to client after entering to NEW_SAVING state.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org