It happens after we redeploy the application. There might be changes to our model, in this scenario an enum is the problem, we added values to it. We switched persistence of.
We currently have multiple instances of our application running. We redeploy them one by one so we can guarantee 24/7 uptime. If using Ignite implies we loose 24/7 uptime, that is an unexpected and unwelcome surprise. The Ignite instances are embedded, so when we start the application (java / spring) Ignite is automatically started in the same JVM as the application (by the application). In my opinion, Ignite should not care about the structure/content of our model. I can't give a quick reproducer. I can post our spring configuration class content, but then you won't have our application and our domain model, so I don't know if that would be of any help. Kind regards, Roger Janssen -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
