zhuzhurk edited a comment on pull request #18566: URL: https://github.com/apache/flink/pull/18566#issuecomment-1031190700
Thanks for opening this PR! @zentol I think it can be quite helpful if users can see the deploying time. In my understanding, it can well measure how fast a job can start working after submitted. I have two questions for the definition of the deploying time: 1. Should the deploying time also include `SCHEDULED` time? In my production experience, users can hardly distinguish scheduling and deploying, and the 2 period together makes a `period before the job starts working`. 2. Looks to me it is not very accurate for the different definition of deploying time for streaming and batch jobs. Streaming jobs can have multiple pipelined regions, part of which may be deploying(especially in failure recovery) and others can be running. Batch jobs can have pipelined edges, and each region needs to run at the same time. Personally, I think the definition you give for streaming jobs is good enough. What do you think of use the same definition for batch jobs, and we simply say that the deploying time ticks whenever there is an ongoing deployment? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
