[
https://issues.apache.org/jira/browse/FLINK-19402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17202030#comment-17202030
]
Chesnay Schepler commented on FLINK-19402:
------------------------------------------
In 1.12 we are introducing a new INITIALIZING state for jobs, for which the
corresponding timestamp effectively is the time when the job submission arrived
on the cluster. With this we can calculate the time required for the job to
start with {{timeStamp(RUNNING) - timeStamp(INITIALIZATING)}}.
Would this be sufficient for you?
> Metrics for measuring Flink application deployment latency in Yarn
> ------------------------------------------------------------------
>
> Key: FLINK-19402
> URL: https://issues.apache.org/jira/browse/FLINK-19402
> Project: Flink
> Issue Type: Improvement
> Components: Deployment / YARN
> Reporter: Yu Yang
> Priority: Major
>
> Real-time streaming applications often have strict down-time SLO during
> deployment. We are trying to measure the Flink job deployment latency on yarn
> cluster. That is the elapsed time between flink job submission to the yarn
> cluster, and the flink job gets up and running.
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
