; user@flink.apache.org
Subject: Re: state access causing segmentation fault
This email is from an external source - exercise caution regarding links and
attachments.
Hi Edward,
could you try adding the static keyword to ExecQueue and RingBufferExec? As is
they hold a reference to the
gt;
> for (java.lang.StackTraceElement s:e.getStackTrace())
>
> LOG.error(s.toString());
>
> }
>
> }
>
> public class ExecQueue {
>
> public RingBufferExec queue;
>
> public ExecQueue (){}
>
: Dawid Wysakowicz mailto:dwysakow...@apache.org>>
Sent: Thursday, October 8, 2020 6:26 AM
To: Colletta, Edward mailto:edward.colle...@fmr.com>>;
user@flink.apache.org<mailto:user@flink.apache.org>
Subject: Re: state access causing segmentation fault
Hi,
It should be absolutely fine
Hi,
It should be absolutely fine to use multiple state objects. I am not
aware of any limits to that. A minimal, reproducible example would
definitely be helpful. For those kind of exceptions, I'd look into the
serializers you use. Other than that I cannot think of an obvious reason
for that kind
Using Flink 1.9.2, Java, FsStateBackend. Running Session cluster on EC2
instances.
I have a KeyedProcessFunction that is causing a segmentation fault, crashing
the flink task manager. The seems to be caused by using 3 State variables in
the operator. The crash happens consistently after some
