[ https://issues.apache.org/jira/browse/FLINK-35108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gyula Fora closed FLINK-35108. ------------------------------ Fix Version/s: kubernetes-operator-1.9.0 Resolution: Fixed merged to main be3b79b64440065c9ae9d3eb0267e412d81ef67e > 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 > Fix For: kubernetes-operator-1.9.0 > > > 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)