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

[Manik Surtani (JIRA)]

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

Manik Surtani commented on ISPN-1365:
-------------------------------------

You can register a listener for a merge view and reconcile (re-write) the data on your own.  Infinispan does not automatically deal with eventual consistency (partition tolerance) yet.

> 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