[infinispan-issues] [JBoss JIRA] (ISPN-4343) Rest rolling upgrades, distributed -- new cluster can't load from old cluster properly

[Tomas Sykora (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-4343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973773#comment-12973773 ] 

Tomas Sykora commented on ISPN-4343:
------------------------------------

[~NadirX] I did some testing around and I have find a few interesting things:

1) The same scenario for HotRod rolling upgrades works. Even though I can see a JGRP000010 message there as well. Anyway, I will fix the test to completely avoid this.

2) I avoid JGRP000010 in REST rolling upgrades test (using +1 switch here):
a) <socket-binding name="jgroups-udp" port="55200" multicast-address="234.99.54.15" multicast-port="45689"/>
b) <socket-binding name="jgroups-mping" port="55200" multicast-address="234.99.54.15" multicast-port="45701"/> and
c) <socket-binding name="modcluster" port="0" multicast-address="224.0.1.116" multicast-port="23365"/> 

This differentiate cluster pretty well, I suppose. 

Old cluster's cache-container name is *clustered*. New cluster's cache-container name is *clustered-new* -- I consider this OK as HotRod rolling upgrades are passing.

When I use approach stated in 2), HotRod RU are passing, but REST RU have still the same issue and just without JGroups complaining about different versions and dropping packets.

Any thoughts Tristan? It looks like I've wasted all my ideas for now.
Thank you! 


> 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
>          Components: Loaders and Stores, Server
>    Affects Versions: 7.0.0.Alpha4
>            Reporter: Tomas Sykora
>            Assignee: Dan Berindei
>            Priority: Critical
>              Labels: rolling_upgrade
>         Attachments: ISPN-4343.txt, ISPN-4343.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



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)