[
https://issues.apache.org/jira/browse/YARN-5855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16145873#comment-16145873
]
Jian He commented on YARN-5855:
-------------------------------
Right now, the behavior after YARN-6903 is:
For stopService , it is still asynchronous, the command does not wait for app
to be stopped
For deleteService (stop + destroy), it is now a synchronous operation:
- it first tries to stop the app and wait for the app to be fully stopped.
- If the app is not stopped, it will forcefully kill the application by
yarnClient.killApplication which waits until the app to be fully stopped.
> 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: [email protected]
For additional commands, e-mail: [email protected]
