[infinispan-issues] [JBoss JIRA] (ISPN-2574) Segment transfer not restarted if the owner fails
Adrian Nistor (JIRA)
jira-events at lists.jboss.org
Thu Dec 6 08:43:17 EST 2012
[ https://issues.jboss.org/browse/ISPN-2574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12739921#comment-12739921 ]
Adrian Nistor edited comment on ISPN-2574 at 12/6/12 8:41 AM:
--------------------------------------------------------------
Closing this so it can go to QE.
Created a separate issue for the unit test: ISPN-2596
was (Author: anistor):
Closing this so it can go to QE.
Created a separate issue for the unit test: ISPN-2569
> Segment transfer not restarted if the owner fails
> -------------------------------------------------
>
> Key: ISPN-2574
> URL: https://issues.jboss.org/browse/ISPN-2574
> Project: Infinispan
> Issue Type: Bug
> Components: State transfer
> Affects Versions: 5.2.0.Beta4
> Reporter: Radim Vansa
> Assignee: Adrian Nistor
> Priority: Critical
> Fix For: 5.2.0.CR1
>
>
> Imagine this situation in distributed cache with 3 owners:
> 1) The segment X is owned by nodes A, B, C
> 2) Node B fails -> CH_UPDATE and then REBALANCE_START are broadcasted
> 3) Node D starts transfer of segment X from C
> 4) Node C fails -> another CH_UPDATE is broadcasted
> 5) D handes the CH_UPDATE and removes the transfer of segment X from C, but does not start another transfer from A
> The {{addedSegments}} does not contain the restarted transfer, because all transfers from write consistent hash are removed from it in the beginning - the segment is considered received here although the transfer is still in progress.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the infinispan-issues
mailing list