A common pitiful when upgrading a Flink application with savepoints is that no explicit UIDs have been assigned to the operators. You can amend that by first adding UIDs to the job in 1.9.3 and create a savepoint with UIDs. Then try upgrading again.
On Fri, Feb 19, 2021 at 9:57 AM Tzu-Li (Gordon) Tai <tzuli...@apache.org> wrote: > Hi, > > I'm not aware of any breaking changes in the savepoint formats from 1.9.3 > to > 1.11.3. > > Let's first try to rule out any obvious causes of this: > - Were any data types / classes that were used in state changed across the > restores? Remember that keys types are also written as part of state > snapshots. > - Did you register any Kryo types in the 1.9.3 execution, had changed those > configuration across the restores? > - Was unaligned checkpointing enabled in the 1.11.3 restore? > > As of now it's a bit hard to debug this with just an EOFException, as the > corrupted read could have happened anywhere before that point. If it's > possible to reproduce a minimal job of yours that has the same restore > behaviour, that could also help a lot. > > Thanks, > Gordon > > > > -- > Sent from: > http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/ >
