Hi Xinmin, Are you getting this error for your custom objects? If yes, did you change a type of a field in those objects?
Probably, you're hitting this problem: https://www.gridgain.com/docs/latest/perf-troubleshooting-guide/troubleshooting#cluster-doesnt-start-after-field-type-changes - Denis On Tue, Sep 8, 2020 at 11:42 AM xmw45688 <[email protected]> wrote: > Hi Denis, I have the same issue when persistenceEnabled = true and when > Ignite is upgrade from 2.8.0 to 2.8.1. The data has been stored in the > disk (single node) running on Ignite 2.8.0. This exception happens for > persistence classes that do not implement java.io.serializable when > upgrading to 2.8.1. Adding java.io.serializable does not resolve this > exception. > > In general when persistenceEnabled = true and the data is stored in the > disk > 1) how to resolve the discrepancies issues of Ignite internal > implementation > between Ignite releases, i.e. the issue I'm experiencing. > 2) how to resolve the key and value class changes (add/remove variables) > > Thanks, > Xinmin > > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
