[
https://issues.apache.org/jira/browse/FLINK-19909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17224244#comment-17224244
]
Yang Wang commented on FLINK-19909:
-----------------------------------
[~kkl0u] Thanks for your response. Hmm. Actually, I find this issue when I am
test K8s native HA. I have two questions here.
* Why we are throwing {{ApplicationExecutionException}} in
{{ApplicationDispatcherBootstrap#runApplicationEntryPoint}}, not
{{ApplicationFailureException}}? If we submit the Flink application with
{{execution.attached: true}}, and we cancel the job, then we still go into the
fatal error handler. Because we only try to find the
{{ApplicationFailureException}}.
* Using the {{ClusterEntrypoint#onFatalError}} is not reasonable, it will make
us have no chance to deregister the Flink application.
> 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
> Priority: Critical
> 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)
