[
https://issues.apache.org/jira/browse/FLINK-19909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kostas Kloudas closed FLINK-19909.
----------------------------------
Resolution: Fixed
master: 2422fb5fc9da3aac95bbd52a6cac7d11479c1ae1
1.11: eb5914419a33a7358384bfc20d6dda0259baff0f
> 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, 1.11.3
> Reporter: Yang Wang
> Assignee: Kostas Kloudas
> Priority: Blocker
> Labels: pull-request-available
> Fix For: 1.12.0, 1.11.3
>
> Attachments: log.jm
>
>
> 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)
