[ https://issues.apache.org/jira/browse/YARN-659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13684136#comment-13684136 ]
Maysam Yabandeh commented on YARN-659: -------------------------------------- But, it seems that FileSystemRMStateStore uses the "attempts" field of ApplicationState: {code:java} @Override public synchronized void removeApplicationState(ApplicationState appState) throws Exception { String appId = appState.getAppId().toString(); Path nodeRemovePath = getNodePath(rmAppRoot, appId); LOG.info("Removing info for app: " + appId + " at: " + nodeRemovePath); deleteFile(nodeRemovePath); for(ApplicationAttemptId attemptId : appState.attempts.keySet()) { removeApplicationAttemptState(attemptId.toString()); } } {code} > RMStateStore's removeApplication APIs should just take an applicationId > ----------------------------------------------------------------------- > > Key: YARN-659 > URL: https://issues.apache.org/jira/browse/YARN-659 > Project: Hadoop YARN > Issue Type: Sub-task > Components: resourcemanager > Reporter: Vinod Kumar Vavilapalli > > There is no need to give in the whole state for removal - just an ID should > be enough when an app finishes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira