]
Pedro Ruivo commented on ISPN-4343:
-----------------------------------
IMO, I think the codec needs to change. I didn't try it yet, but my idea is to change
the codec to put the data as key and put the data type in the MimeMetadata. then we can
get rid of MimeCacheEntry.
Rest rolling upgrades, distributed -- new cluster can't load from
old cluster properly
--------------------------------------------------------------------------------------
Key: ISPN-4343
URL:
https://issues.jboss.org/browse/ISPN-4343
Project: Infinispan
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Loaders and Stores, Server
Affects Versions: 7.0.0.Alpha4
Reporter: Tomas Sykora
Assignee: Tomas Sykora
Priority: Critical
Labels: rolling_upgrade
Attachments: cannot_be_cast.txt, clustered-rest-rolling-upgrade.xml,
clustered.xml, ISPN-4343.txt, ISPN-4343.zip, restRollUpsTraceLog.zip
A try to mimic the process of REST Rolling Upgrades for one old and new server in a
clustered environment failed.
Scenario is quite simple, we start 2 old servers, store some data in, start 2 new servers
and point clients to that new cluster.
When issuing a get on a new cluster (want to fetch old entry from old store), the
operation fails with attached stack trace.
I also include current ISPN testsuite where is added
testRestRollingUpgradesDiffVersionsDist test as a reproducer.
Respective changes are mirrored in my remote branch:
https://github.com/tsykora/infinispan/tree/ISPN-4330
You can run test like:
mvn clean verify -P suite.rolling.upgrades
-Dzip.dist.old=/home/you/servers/previous-ispn-server-version.zip
-Dtest=RestRollingUpgradesTest#testRestRollingUpgradesDiffVersionsDist