Sweet, thanks Aljoscha for the quick help.
Gyula
Aljoscha Krettek ezt írta (időpont: 2017. aug. 10.,
Cs, 15:33):
> Don't worry! :-) I found that you can configure this via
> "high-availability.job.delay"
> (in HighAvailabilityOptions).
>
> Best,
> Aljoscha
>
> On 10. Aug 2017, at 15:13, Gyula
Don't worry! :-) I found that you can configure this via
"high-availability.job.delay" (in HighAvailabilityOptions).
Best,
Aljoscha
> On 10. Aug 2017, at 15:13, Gyula Fóra wrote:
>
> Here is actually the whole log for the relevant parts at least:
> https://gist.github.com/gyfora/b70dd18c048b8
Here is actually the whole log for the relevant parts at least:
https://gist.github.com/gyfora/b70dd18c048b862751b194f613514300
Sorry for not pasting it earlier.
Gyula
Gyula Fóra ezt írta (időpont: 2017. aug. 10., Cs,
15:04):
> Oh, I found this in the log that seems to explain it: 2017-08-10
>
Oh, I found this in the log that seems to explain it: 2017-08-10
13:13:56,795 INFO org.apache.flink.yarn.YarnJobManager - Delaying recovery
of all jobs by 12 milliseconds.
I wonder why is this...
Aljoscha Krettek ezt írta (időpont: 2017. aug. 10.,
Cs, 14:41):
> Hi,
>
> Let me also investiga
Hi,
Let me also investigate that? Did you observe this in 1.3.2 and not in 1.3.0
and/or 1.3.1 or did you directly go from 1.2.x to 1.3.2?
Best,
Aljoscha
> On 10. Aug 2017, at 13:31, Gyula Fóra wrote:
>
> Hi!
> In some cases it seems to take a long time for the job to start the zookeeper
> ba
Hi!
In some cases it seems to take a long time for the job to start the
zookeeper based job recovery after recovering from a JM failure.
Looking at the logs there is a 2 minute gap between the last recovered TM
was started successfully and the job recovery:
2017-08-10 13:14:06,369 INFO
org.apache.