You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by "Yang Wang (Jira)" <ji...@apache.org> on 2020/11/01 07:46:00 UTC
[jira] [Created] (FLINK-19909) Flink application in attach mode
could not terminate when the only job is canceled
Yang Wang created FLINK-19909:
---------------------------------
Summary: Flink application in attach mode could not terminate when the only job is canceled
Key: FLINK-19909
URL: https://issues.apache.org/jira/browse/FLINK-19909
Project: Flink
Issue Type: Bug
Components: Deployment / Kubernetes, Deployment / YARN, Runtime / Coordination
Affects Versions: 1.12.0
Reporter: Yang Wang
Fix For: 1.12.0
Currently, the Yarn and Kubernetes application in attach mode could not terminate the Flink cluster after the only job is canceled. Because we are throwing {{ApplicationExecutionException}} in {{ApplicationDispatcherBootstrap#runApplicationEntryPoint}}. However, we are only checking {{ApplicationFailureException}} in {{runApplicationAndShutdownClusterAsync}}. Then we will go to fatal error handler which make the jobmanager directly exits. And it has no chance to deregister itself to the cluster manager(Yarn/Kubernetes). That means the jobmanager will be relaunched by cluster manager again and again until it exhausts the retry attempts.
cc [~kkl0u], I am not sure is this an expected change? I think it could work in 1.11.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)