GitHub user barcahead opened a pull request: https://github.com/apache/flink/pull/3640
[FLINK-6213] [yarn] terminate resource manager itself when shutting down application When number of failed containers exceeds maximum failed containers, `YarnFlinkResourceManager` will receive msg `StopCluster` and then invoke `shutdownApplication`. In this method, it calls `amrmclient.unregisterApplicationMaster` to finish the application. But the AM container is not released until 10 minutes later triggered by RM ping check timeout. I fix this issue by terminating resource manager itself after unregistering application master, then the process will exit and the container will be released. You can merge this pull request into a Git repository by running: $ git pull https://github.com/barcahead/flink FLINK-6213 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/flink/pull/3640.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #3640 ---- commit 1f4c91af090189d8a797a500701689b6639c4a85 Author: fengyelei <fengye...@huawei.com> Date: 2017-03-29T03:40:24Z [FLINK-6213] [yarn] terminate resource manager itself when shutting down application ---- --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---