[infinispan-issues] [JBoss JIRA] (ISPN-4310) StateResponse chunk with lastChunk=true from cancelled ST stops receiving data in next ST

RH Bugzilla Integration (JIRA) issues at jboss.org
Thu Jun 12 12:11:38 EDT 2014


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

RH Bugzilla Integration commented on ISPN-4310:
-----------------------------------------------

Dan Berindei <dberinde at redhat.com> changed the Status of [bug 1104031|https://bugzilla.redhat.com/show_bug.cgi?id=1104031] from NEW to POST

> StateResponse chunk with lastChunk=true from cancelled ST stops receiving data in next ST
> -----------------------------------------------------------------------------------------
>
>                 Key: ISPN-4310
>                 URL: https://issues.jboss.org/browse/ISPN-4310
>             Project: Infinispan
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: State Transfer
>    Affects Versions: 6.0.2.Final, 7.0.0.Alpha4
>            Reporter: Radim Vansa
>            Assignee: Dan Berindei
>            Priority: Critical
>              Labels: 63gablocker
>             Fix For: 7.0.0.Alpha5
>
>
> 1. A requests segment from B (there are multiple chunks)
> 2. B sends all chunks, but before A receives them, new topology arrives and A cancels the ST.
> 3. Another topology comes and A requests this segment again
> 4. A receives the old StateResponseCommand with lastChunk=true and thinks that it got all segments, therefore, it discards further chunks.
> Result is inconsistent cluster, and after further rebalances completely lost data.
> This ought to be rare, but was repeatedly observed when gracefully stopping coordinator on a 32-node cluster full of data.



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


More information about the infinispan-issues mailing list