Thank you all for the help, it is appreciated!
2015-06-29 9:12 GMT+01:00 Stephan Ewen :
> Hi Nuno!
>
> Ultimately, the delay is a property of the ExecutionGraph. The
> ExecutionGraph is the data structure on the master (JobManager) that tracks
> the distributed execution.
>
> The property is set
Hi Nuno!
Ultimately, the delay is a property of the ExecutionGraph. The
ExecutionGraph is the data structure on the master (JobManager) that tracks
the distributed execution.
The property is set in the method "JobManager.submitJob(...)", which is
called when a new job is sent to the cluster.
Hop
Done
On Mon, Jun 29, 2015 at 9:33 AM, Chiwan Park wrote:
> We should assign FLINK-2066 to Nuno. :)
>
> Regards,
> Chiwan Park
>
> > On Jun 29, 2015, at 1:21 PM, Márton Balassi
> wrote:
> >
> > Hey,
> >
> > Thanks for picking up the issue. This value can be specified as
> > "execution-retries.de
We should assign FLINK-2066 to Nuno. :)
Regards,
Chiwan Park
> On Jun 29, 2015, at 1:21 PM, Márton Balassi wrote:
>
> Hey,
>
> Thanks for picking up the issue. This value can be specified as
> "execution-retries.delay" in the flink-conf.yaml. Hence you can check the
> associated value in the C
Hey,
Thanks for picking up the issue. This value can be specified as
"execution-retries.delay" in the flink-conf.yaml. Hence you can check the
associated value in the ConfigConstants [1] and track the way it is used.
It is passed a couple of times, but is ultimately used in ExecutionGraph.
[2]
[1
