[ https://issues.apache.org/jira/browse/YARN-5855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16146130#comment-16146130 ]
Jian He commented on YARN-5855: ------------------------------- Talked with Gour, if we have YARN-2261 or YARN-5759, then the DELETE can be a fast asynchronous call as well. Yarn will take care of deleting the left over records. Once that feature is complete, the delete can be revisited. > DELETE call sometimes returns success when app is not deleted > ------------------------------------------------------------- > > Key: YARN-5855 > URL: https://issues.apache.org/jira/browse/YARN-5855 > Project: Hadoop YARN > Issue Type: Sub-task > Reporter: Billie Rinaldi > Assignee: Gour Saha > > Looking into this issue with [~gsaha], we noticed that multiple things can > contribute to an app continuing to run after a DELETE call, which consists of > a stop and a destroy operation. One problem is that the stop call is > asynchronous unless a force flag is set. Without the force flag, a message is > sent to the AM and success is returned, and with the flag > yarnClient.killRunningApplication is called. (There is also an option to wait > for a fixed amount of time for the app to stop before returning, but DELETE > is not setting this option and force is preferable in this case.) The other > issue is that the destroy operation is attempted in a loop, but if the number > of retries is exceeded the call returns a 204 response. -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org