[infinispan-issues] [JBoss JIRA] Commented: (ISPN-1365) Data left in inconsistent state on rehash.
[
https://issues.jboss.org/browse/ISPN-1365?page=com.atlassian.jira.plugin....
]
Dan Berindei commented on ISPN-1365:
------------------------------------
I've run the test a few times and I got two kinds of errors:
1. The test didn't create all caches when starting up a node, so sometimes the alloc
cache is not created at all on a node and the cluster is never properly form.
2. Most other times the cluster is formed through a succession of merges. The test
doesn't wait for all the nodes to join the cluster, so it is possible for two
transactions to write to the same key on two different partitions and then one of those
values will be lost on merge.
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