[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15414763#comment-15414763 ] Rohith Sharma K S commented on YARN-5477: - Closed as duplicate. > 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-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15414636#comment-15414636 ] Naganarasimha G R commented on YARN-5477: - Yes [~rohithsharma], here too we were thinking the same, Shall we close this jira, thoughts? > 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-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15413931#comment-15413931 ] Rohith Sharma K S commented on YARN-5477: - Basically issue is with user facing App states. There is improvement task YARN-3232(patch available) exist for removing few states which are not necessarily exposed to users. I think, It would be better to continue over there. > 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-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
