[infinispan-issues] [JBoss JIRA] (ISPN-9620) Rolling Upgrade Marshaller Changes
Gustavo Fernandes (Jira)
issues at jboss.org
Mon Nov 4 02:41:00 EST 2019
[ https://issues.jboss.org/browse/ISPN-9620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13807477#comment-13807477 ]
Gustavo Fernandes edited comment on ISPN-9620 at 11/4/19 2:40 AM:
------------------------------------------------------------------
"Protocol buffers should be utilised as the wire/storage format, with protostream providing the implementation."
Is about a core-scoped rolling upgrade? Or related to the current Rolling Upgrade that happens over hot rod?
For the current procedure, a server can store data in any format: JBoss marshalled, UTF-8, protostream, octect-stream, etc.
When migrating data from a cluster to another, it all happens via Hot Rod with "raw" data, that is, data is iterated in the source cluster and stored in the new cluster in the same format, so it does not make sense to use the same marshaller between two clusters
was (Author: gustavonalle):
"Protocol buffers should be utilised as the wire/storage format, with protostream providing the implementation."
Not sure I understand this, as a server can store data in any format: JBoss marshalled, UTF-8, protostream, octect-stream, etc.
When migrating data from a cluster to another via Rolling Upgrade, it all happens via Hot Rod with "raw" data, that is, data is iterated in the source cluster and stored in the new cluster in the same format
> 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)
More information about the infinispan-issues
mailing list