[infinispan-issues] [JBoss JIRA] Updated: (ISPN-1365) Data left in inconsistent state on rehash.

[Dan Berindei (JIRA)]

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

Dan Berindei updated ISPN-1365:
-------------------------------

              Status: Pull Request Sent  (was: Open)
    Git Pull Request: https://github.com/infinispan/infinispan/pull/522


Distributed tasks were allowed to execute on a joining node before it was finished starting. That meant a distributed task could modify a key before the rehash, but then during the rehash another node could push an old value and overwrite it, resulting in data loss.

> Data left in inconsistent state on rehash.
> ------------------------------------------
>
>                 Key: ISPN-1365
>                 URL: https://issues.jboss.org/browse/ISPN-1365
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Core API
>    Affects Versions: 5.0.0.FINAL
>            Reporter: Erik Salter
>            Assignee: Dan Berindei
>             Fix For: 5.1.0.ALPHA1, 5.1.0.FINAL
>
>         Attachments: cacheTest_rehash.zip
>
>
> I'm seeing a lot of data inconsistencies on a rehash, especially if there is a lot of lock contention for keys on caches participating in a transaction.
> Attached is a unit test that can reproduce the problem quite readily.  This uses the grouping API, eager locking of a single node, and the distribution framework to effect "local" transactions.

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