No, that problem I mentioned does not affect batch jobs. Must be something
different then, but unfortunately the dump looks not very helpful to me because
of the „error occurred during error reporting (printing native stack)“.
> Am 14.05.2018 um 14:26 schrieb Flavio Pompermaier :
>
> My job is
My job is a batch one, not a streaming job. Is it possible that the cause
is the one you mentioned?
On Mon, 14 May 2018, 14:23 Stefan Richter,
wrote:
> Hi,
>
> that looks like a known issue where Flink did not wait for the shutdown of
> the timer service before disposing state backends. This is
Hi,
that looks like a known issue where Flink did not wait for the shutdown of the
timer service before disposing state backends. This is problem fixed in the >=
1.4 branches.
Best,
Stefan
> Am 14.05.2018 um 14:12 schrieb Flavio Pompermaier :
>
> Hi to all,
> I have a Flink 1.3.1 job that ru
Hi to all,
I have a Flink 1.3.1 job that runs multiple times.
Everything goes well for some time (e.g. 10 jobs). Then, one or more TMs
suddently die.
In the .out file I find something like this:
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x7f
