[
https://issues.jboss.org/browse/ISPN-9620?page=com.atlassian.jira.plugin....
]
Ryan Emerson commented on ISPN-9620:
------------------------------------
[~gustavonalle] This is built upon what was discussed at last years F2F. It is a long term
goal we're working towards and does not intend to replace the current rolling upgrades
that we have. The idea is that we get to the stage where we can do the following types of
upgrade:
# Offline upgrade (start/stop). Cache stores are dumped using the old ISPN cluster, new
ISPN cluster brought up using the old date.
# [Kuberenetes Rolling
updates|https://kubernetes.io/docs/tutorials/kubernetes-basics/update/update-intro/]. This
is the long term goal, which requires more than marshalling changes, e.g. versioned
interceptor stacks. The marshalling changes are required in this context to allow over the
air compatibility between ISPN versions.
Rolling Upgrade Marshaller Changes
----------------------------------
Key: ISPN-9620
URL:
https://issues.jboss.org/browse/ISPN-9620
Project: Infinispan
Issue Type: Enhancement
Components: Core, Loaders and Stores
Affects Versions: 9.4.0.Final
Reporter: Ryan Emerson
Assignee: Ryan Emerson
Priority: Major
Fix For: 10.1.0.Final
In order to allow for compatibility between infinispan versions it is necessary for us to
utilise a marshalling implementation at both the cluster (internal node-to-node
communication) and persistence layer that is strictly defined but allows for future
changes. This is necessary in order to facilitate both rolling and start/stop upgrades.
Protocol buffers should be utilised as the wire/storage format, with protostream providing
the implementation.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)