Hi Bekir, Before diving deeper, just to rule out the obvious: Have you changed anything with the element type of the input stream to the async wait operator?
This wasn't apparent from the information so far, so I want to quickly clear that out of the way first. Cheers, Gordon On Wed, Oct 30, 2019 at 11:52 PM Bekir Oguz <bekir.o...@dpgmedia.nl> wrote: > Hi guys, > during our upgrade from 1.8.1 to 1.9.1, one of our jobs fail to start with > the following exception. We deploy the job with 'allow-non-restored-state' > option and from the latest checkpoint dir of the 1.8.1 version. > > org.apache.flink.util.StateMigrationException: The new state typeSerializer > for operator state must not be incompatible. > at org.apache.flink.runtime.state.DefaultOperatorStateBackend > .getListState(DefaultOperatorStateBackend.java:323) > at org.apache.flink.runtime.state.DefaultOperatorStateBackend > .getListState(DefaultOperatorStateBackend.java:214) > at org.apache.flink.streaming.api.operators.async.AsyncWaitOperator > .initializeState(AsyncWaitOperator.java:272) > at org.apache.flink.streaming.api.operators.AbstractStreamOperator > .initializeState(AbstractStreamOperator.java:281) > at org.apache.flink.streaming.runtime.tasks.StreamTask.initializeState( > StreamTask.java:881) > at > org.apache.flink.streaming.runtime.tasks.StreamTask.invoke(StreamTask > .java:395) > at org.apache.flink.runtime.taskmanager.Task.doRun(Task.java:705) > at org.apache.flink.runtime.taskmanager.Task.run(Task.java:530) > at java.lang.Thread.run(Thread.java:748) > > We see from the Web UI that the 'async wait operator' is causing this, > which is not changed at all during this upgrade. > > All other jobs are migrated without problems, only this one is failing. Has > anyone else experienced this during migration? > > Regards, > Bekir Oguz >
