You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Chesnay Schepler (Jira)" <ji...@apache.org> on 2022/06/09 11:54:00 UTC
[jira] [Comment Edited] (FLINK-27473) Capture time that a job spends on initializing tasks
[ https://issues.apache.org/jira/browse/FLINK-27473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17552152#comment-17552152 ]
Chesnay Schepler edited comment on FLINK-27473 at 6/9/22 11:53 AM:
-------------------------------------------------------------------
not quite; you need to make sure to not overlap with deploying time introduced in FLINK-25888.
The end goal is to split the running time (i.e., the time when Flink reports the job as RUNNING) into 3 distinct sections; one each for deploying/initializing/running(like, _actually_ running).
So it would be something like:
* for batch jobs, if no task is running and at least one task is being initialized
** this also implies a change to the deployment metric semantics, such that a batch job is running "if not task is initializing and at least one task is being deployed)
* for streaming jobs, if no task is deploying and at least one task is being initialized
So the general rules stay the same, you just also make sure that earlier states take precedence. (I.e., we aren't running when something is deploying/initializing, and not initializing when something is deploying).
was (Author: zentol):
not quite; you need to make sure to not overlap with deploying time introduced in FLINK-25888.
The end goal is to split the running time into 3 distinct sections; one each for deploying/initializing/running.
So it would be something like:
* for batch jobs, if no task is running and at least one task is being initialized
** this also implies a change to the deployment metric semantics, such that a batch job is running "if not task is initializing and at least one task is being deployed)
* for streaming jobs, if no task is deploying and at least one task is being initialized
So the general rules stay the same, you just also make sure that earlier states take precedence. (I.e., we aren't running when something is deploying/initializing, and not initializing when something is deploying).
> Capture time that a job spends on initializing tasks
> ----------------------------------------------------
>
> Key: FLINK-27473
> URL: https://issues.apache.org/jira/browse/FLINK-27473
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Coordination, Runtime / Metrics
> Reporter: Jun Qin
> Priority: Major
>
> Similar to https://issues.apache.org/jira/browse/FLINK-25888, we should have it also for initializing tasks.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)