[FLINK-19909] Flink application in attach mode could not terminate when the only job is canceled

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 1.11.3, 1.12.0
• Fix Version/s: 1.11.3, 1.12.0
• Component/s: Deployment / Kubernetes, Deployment / YARN, Runtime / Coordination
• Labels: pull-request-available
• Assignee: Kostas Kloudas
• Reporter: Yang Wang
• Created: 01/Nov/20 07:45
• Updated: 06/Nov/20 09:25
• Resolved: 06/Nov/20 08:55

Description

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 Kostas Kloudas, I am not sure is this an expected change? I think it could work in 1.11.

Issue Links

• is caused by: FLINK-19154 Application mode deletes HA data in case of suspended ZooKeeper connection
• links to: GitHub Pull Request #13911