Chesnay Schepler created FLINK-25888:
----------------------------------------
Summary: Capture time that the job spends on deploying tasks
Key: FLINK-25888
URL: https://issues.apache.org/jira/browse/FLINK-25888
Project: Flink
Issue Type: New Feature
Components: Runtime / Coordination, Runtime / Metrics
Reporter: Chesnay Schepler
Assignee: Chesnay Schepler
Fix For: 1.15.0
FLINK-23976 added standardized metrics for capturing how much time we spend in
each {{JobStatus}}. However, certain states in practice consist of several
stages; for example the RUNNING state also includes the deployment of tasks.
To get a better picture on where time is spent I propose to add new metrics
that capture the deployingTime based on the execution states. This will
additionally get us closer to a proper uptime metric, which ideally will be
runningTime - various stage time metrics.
A job is considered to be deploying,
* for batch jobs, if no task is running and at least one task is being deployed
* for streaming jobs, if at least one task is being deployed
The semantics are different for batch/streaming jobs because they differ in
terms of how they make progress. For a streaming job all tasks need to be
deployed for checkpointing to make work. For batch jobs any deployed task
immediately starts progressing the job.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
