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

Posted to issues@flink.apache.org by "yuanfenghu (Jira)" <ji...@apache.org> on 2025/03/31 07:16:00 UTC

[jira] [Created] (FLINK-37588) Flink Kubernetes Operator Parameter `jm-deployment.shutdown-ttl` does not take effect

yuanfenghu created FLINK-37588:
----------------------------------

             Summary: Flink Kubernetes Operator Parameter `jm-deployment.shutdown-ttl` does not take effect
                 Key: FLINK-37588
                 URL: https://issues.apache.org/jira/browse/FLINK-37588
             Project: Flink
          Issue Type: Bug
          Components: Kubernetes Operator
            Reporter: yuanfenghu


When I configured jm-deployment.shutdown-ttl, it did not take effect because its judgment was based on the JobStatus#updateTime, but this parameter will only change if state changes are observed in two previous observations, and observations are triggered periodically. Therefore, if the time difference between the last state change and the current time after we stop the task exceeds jm-deployment.shutdown-ttl, the cluster will be destroyed immediately. This is not expected, so we should also update updateTime when the task state is manually triggered to change to FINISHED.



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