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

Posted to issues@flink.apache.org by "Rui Fan (Jira)" <ji...@apache.org> on 2024/03/21 10:13:00 UTC

[jira] [Created] (FLINK-34907) jobRunningTs should be the timestamp that all tasks are running

Rui Fan created FLINK-34907:
-------------------------------

             Summary: jobRunningTs should be the timestamp that all tasks are running
                 Key: FLINK-34907
                 URL: https://issues.apache.org/jira/browse/FLINK-34907
             Project: Flink
          Issue Type: Improvement
          Components: Autoscaler
            Reporter: Rui Fan
            Assignee: Rui Fan
             Fix For: kubernetes-operator-1.9.0


Currently, we consider the timestamp that JobStatus is changed to RUNNING as jobRunningTs. But the JobStatus will be RUNNING once job starts schedule, so it doesn't mean all tasks are running. 

It will let the isStabilizing or estimating restart time are not accurate.

Solution: jobRunningTs should be the timestamp that all tasks are running.

It can be got from SubtasksTimesHeaders rest api.




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