Hi, I understand and experience that Ignite crashes (binaryobjectexceeptions) when I redeploy my application (with an embedded Ignite server node) in a cluster and the new redeployed application has a different model (like enums with added values).
This results in the inability to have my application up 24/7 because I can't do rolling updates. It suggest I need to kill all my application instances (and thus the embedded Ignite instances) first and then deploy and restart them. But this is not acceptable. How do I need to configure Ignite to be able to do rolling updates with changing models? If this is not possible, what is the use of Ignite as a distributed cache? Configuration details: - server nodes only - non persistent - cached replicated (in fact I am only interested in distributed cache invalidations) - server nodes run embedded in/from a java/spring/tomcat application Kind regards, Roger Janssen -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
