Hi Flavio, This is a daunting task to implement properly. There is an easy fix in related workflow systems though. Assuming that it's a rerunning task, then you simply store the run times of the last run, use some kind of low-pass filter (=decaying average) and compare the current runtime with the expected runtime. Even if Flink would have some estimation, it's probably not more accurate than this.
Best, Arvid On Tue, Aug 11, 2020 at 10:26 AM Robert Metzger <rmetz...@apache.org> wrote: > Hi Flavio, > > I'm not aware of such a heuristic being implemented anywhere. You need to > come up with something yourself. > > On Fri, Aug 7, 2020 at 12:55 PM Flavio Pompermaier <pomperma...@okkam.it> > wrote: > >> Hi to all, >> one of our customers asked us to see a percentage of completion of a >> Flink Batch job. Is there any already implemented heuristic I can use to >> compute it? Will this be possible also when DataSet api will migrate to >> DataStream..? >> >> Thanks in advance, >> Flavio >> > -- Arvid Heise | Senior Java Developer <https://www.ververica.com/> Follow us @VervericaData -- Join Flink Forward <https://flink-forward.org/> - The Apache Flink Conference Stream Processing | Event Driven | Real Time -- Ververica GmbH | Invalidenstrasse 115, 10115 Berlin, Germany -- Ververica GmbH Registered at Amtsgericht Charlottenburg: HRB 158244 B Managing Directors: Timothy Alexander Steinert, Yip Park Tung Jason, Ji (Toni) Cheng
