[
https://issues.apache.org/jira/browse/FLINK-26772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17525441#comment-17525441
]
Matthias Pohl edited comment on FLINK-26772 at 4/21/22 6:37 AM:
----------------------------------------------------------------
[~wangyang0918] pointed out that SIGTERM is triggered when unregistering the
cluster from k8s (which deletes the deployment). That makes k8s send SIGTERM to
the pods. FLINK-21008 covered this issue. This issue is also present in YARN
setups according to the comments in FLINK-21008.
was (Author: mapohl):
[~wangyang0918] pointed out that SIGTERM is triggered when unregistering the
cluster from k8s (which deletes the deployment). That makes k8s send SIGTERM to
the pods. FLINK-21008 covered this issue.
> Application Mode does not wait for job cleanup during shutdown
> --------------------------------------------------------------
>
> Key: FLINK-26772
> URL: https://issues.apache.org/jira/browse/FLINK-26772
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Coordination
> Affects Versions: 1.15.0
> Reporter: Mika Naylor
> Assignee: Matthias Pohl
> Priority: Critical
> Labels: pull-request-available
> Attachments: FLINK-26772.standalone-job.log,
> testcluster-599f4d476b-bghw5_log.txt
>
>
> We discovered that in Application Mode, when the application has completed,
> the cluster is shutdown even if there are ongoing resource cleanup events
> happening in the background. For example, if ha cleanup fails, further
> retries are not attempted as the cluster is shut down before this can happen.
>
> We should also add a flag for the shutdown that will prevent further jobs
> from being submitted.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
