[infinispan-issues] [JBoss JIRA] (ISPN-4504) Topology id is not properly set on ClusteredGetCommands

[Dan Berindei (JIRA)]

     [ https://issues.jboss.org/browse/ISPN-4504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dan Berindei updated ISPN-4504:
-------------------------------

    Description: 
Because the topology id is not properly set on ClusteredGetCommands, they don't wait for the sender's topology to be installed on the target.

I have tried to fix this while implementing a fix for ISPN-4503. My solution caused 2 failures in RemoteGetDuringStateTransferTest, scenarios 5 and 7::

|   sc | currentTopologyId         | currentTopologyId + 1 (rebalance)     | currentTopologyId + 2 (finish) |
|   5  | 0:remoteGet               | 2:sendReply                           | 0:receiveReply, 1:sendReply |
|   7  |                           | 0:remoteGet, 2: sendReply             | 0:receiveReply, 1:sendReply |


  was:
Because the topology id is not properly set on ClusteredGetCommands, they don't wait for the sender's topology to be installed on the target.

I have tried to fix this while implementing a fix for ISPN-4503. My solution caused 2 failures in RemoteGetDuringStateTransferTest, scenarios 5 and 7::

|   5  | 0:remoteGet               | 2:sendReply                           | 0:receiveReply, 1:sendReply |
|   7  |                           | 0:remoteGet, 2: sendReply             | 0:receiveReply, 1:sendReply |




> Topology id is not properly set on ClusteredGetCommands
> -------------------------------------------------------
>
>                 Key: ISPN-4504
>                 URL: https://issues.jboss.org/browse/ISPN-4504
>             Project: Infinispan
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Core
>    Affects Versions: 7.0.0.Alpha4
>            Reporter: Dan Berindei
>            Assignee: Dan Berindei
>             Fix For: 7.0.0.Alpha5
>
>
> Because the topology id is not properly set on ClusteredGetCommands, they don't wait for the sender's topology to be installed on the target.
> I have tried to fix this while implementing a fix for ISPN-4503. My solution caused 2 failures in RemoteGetDuringStateTransferTest, scenarios 5 and 7::
> |   sc | currentTopologyId         | currentTopologyId + 1 (rebalance)     | currentTopologyId + 2 (finish) |
> |   5  | 0:remoteGet               | 2:sendReply                           | 0:receiveReply, 1:sendReply |
> |   7  |                           | 0:remoteGet, 2: sendReply             | 0:receiveReply, 1:sendReply |



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)