le threads can work on the same internal serializer state and corrupt
>> it. Will take a deeper look an monday.
>>
>> Best,
>> Stefan
>>
>>> Am 11.08.2017 um 20:55 schrieb Daiqing Li <lidaiqing1...@gmail.com
>>> <mailto:lidaiqing1...@gmail.c
Hi,
I am running fling 1.3.1 on EMR. But I am getting this exception after running
for a while.
java.lang.RuntimeException: Exception occurred while processing valve output
watermark:
at
serialize and pay attention to the entryID map.
>
>> On 10 Aug 2017, at 14:54, Daiqing Li <lidaiqing1...@gmail.com> wrote:
>>
>> Oh sorry, the data in {} is not empty because I hide private information
>> about my model. Do you have that same conclusion?
>
irst {} is your event.toString, which
> seems odd as if your event was empty.
>
> Generally speaking as I understand this Exception is thrown because the
> hashcode of your event changes during serialization, and access to some
> internal temporary cache is broken.
>
>
re your code for that job or at least a minimal example to reproduce
> this behaviour. I fear we won’t be able to help you without any further
> info.
>
> Regards,
> Dawid
>
> > On 10 Aug 2017, at 14:10, Daiqing Li <lidaiqing1...@gmail.com> wrote:
> >
> > Hi Flink us
Hi Flink user,
I am using FsStateBackend and AWS EMR YARN to run a CEP job. I got this
exception after running for a while. Could anyone give me some help to
debug this? I try parallelism 1, and it has the same problem. I also try
reimplemented hashcode and equals method. I use UUID as hashcode
