Re: flink 1.4.2. java.lang.IllegalStateException: Could not initialize operator state backend

The stack trace shows that the state is being restored which has probably already happened after job restart. I am wondering why it has been restarted after some time of running. Could you share full job/task manager logs? On Thu, May 16, 2019 at 6:26 AM anaray wrote: > Thank You Andrey. Arity

Re: flink 1.4.2. java.lang.IllegalStateException: Could not initialize operator state backend

Thank You Andrey. Arity of the job has not changed. Here issue is that job will run for sometime (with checkpoint enabled) and then after some time will get into above exception. The job keeps restarting afterwards. One thing that I want point out here is that we have a custom *serialization

Re: flink 1.4.2. java.lang.IllegalStateException: Could not initialize operator state backend

Hi, I am not sure that FLINK-8836 is related to the failure in the stack trace. You say you are using Flink in production, does it mean it always worked and has started to fail recently? >From the stack trace, it looks like the arity of some

flink 1.4.2. java.lang.IllegalStateException: Could not initialize operator state backend

Hi, We have flink 1.4.2 in production, and we have started seeing below exception consistently. Could some help me understand the real issue happening here? I see that https://issues.apache.org/jira/browse/FLINK-8836 has fixed it, but since it needs an upgrade, we exploring workarounds or other