[infinispan-issues] [JBoss JIRA] Resolved: (ISPN-731) make rehashing state and tx log draining serial

[Vladimir Blagojevic (JIRA)]

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

Vladimir Blagojevic resolved ISPN-731.
--------------------------------------

    Resolution: Done


Fixed on 4.2 and master.

https://github.com/vblagoje/infinispan/commit/03c776a8dd39093fa5ebfb97e447568f811b2845

https://github.com/vblagoje/infinispan/commit/d8b0b3a40fcd80d7e700d4148ade0b6bba1867c7

> make rehashing state and tx log draining serial
> -----------------------------------------------
>
>                 Key: ISPN-731
>                 URL: https://jira.jboss.org/browse/ISPN-731
>             Project: Infinispan
>          Issue Type: Bug
>    Affects Versions: 4.1.0.Final
>            Reporter: Mircea Markus
>            Assignee: Vladimir Blagojevic
>            Priority: Critical
>             Fix For: 4.2.0.CR1, 4.2.0.Final, 5.0.0.BETA1, 5.0.0.Final
>
>
> {A,B,C, D}, num owners= 2. A's state is {(k,v)} and a transactions is prepared with {(k, otherValue)} on A.
> B crashes.
> two things happen with A's state: 
> 1. on C an thread pulls state from A
> 2. A sends transaction state to C on another thread
> Whit the right timing:
> - 2 executes first (tx log is drained)
> - tx commits - this applies the changes on C as well 
> - 1 executes last 
> Data ends up inconsistent:
> A's states is {(k, otherValue)} while C's state is  {(k,v)} 
> State transfer and tx log needs to be sequential (not parallel).
> See the attached email thread for discussions around this.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira