You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2024/04/15 11:50:00 UTC

[jira] [Updated] (FLINK-35108) Deployment recovery is triggered on terminal jobs after jm shutdown ttl

     [ https://issues.apache.org/jira/browse/FLINK-35108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ASF GitHub Bot updated FLINK-35108:
-----------------------------------
    Labels: pull-request-available  (was: )

> Deployment recovery is triggered on terminal jobs after jm shutdown ttl
> -----------------------------------------------------------------------
>
>                 Key: FLINK-35108
>                 URL: https://issues.apache.org/jira/browse/FLINK-35108
>             Project: Flink
>          Issue Type: Bug
>          Components: Kubernetes Operator
>    Affects Versions: kubernetes-operator-1.7.0, kubernetes-operator-1.8.0
>            Reporter: Gyula Fora
>            Assignee: Gyula Fora
>            Priority: Critical
>              Labels: pull-request-available
>
> The deployment recovery mechanism is incorrectly triggered for terminal jobs once the JM deployment is deleted after the TTL period. 
> This causes jobs to be resubmitted. This affects only batch jobs.
> The workaround is to set 
> kubernetes.operator.jm-deployment-recovery.enabled: false
>  for batch jobs.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)