On Wed, May 27, 2015 at 11:02 AM, tcostasouza <[email protected]> wrote:
> Hello Ognen, > > That's the exactly situation I'm trying to avoid. > > One strategy that I'm planning to test is, for each physical cluster node, > fire up a new ignite node with the updated code and the take down the old > one. Effectively doing a rolling update of the cluster. > > But it's hard to tell what would be the effects in application runtime. > One thing for sure, the new code must be backward compatible with the old > one, or else, bad things will follow. > Yeah, one issue will be the mix of old and new classes in the cache as you are "rolling". Especially if you have two different versions of the same class.
