[FLINK-34907] jobRunningTs should be the timestamp that all tasks are running

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Fix Version/s: kubernetes-operator-1.11.0
• Component/s: Autoscaler
• Assignee: Rui Fan
• Reporter: Rui Fan
• Created: 21/Mar/24 10:12
• Updated: 14/Oct/24 16:54

Description

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 doesn't include request TM resources from kubernetes/yarn, deploy tasks and restore states, these steps will take a lot of time).

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.