[infinispan-issues] [JBoss JIRA] Commented: (ISPN-240) Removals not working as expected when L1 is disabled
Manik Surtani (JIRA)
jira-events at lists.jboss.org
Thu Oct 29 08:20:05 EDT 2009
[ https://jira.jboss.org/jira/browse/ISPN-240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12492053#action_12492053 ]
Manik Surtani commented on ISPN-240:
------------------------------------
See http://lists.jboss.org/pipermail/infinispan-dev/2009-October/001739.html for a discussion on the cause and solution.
> Removals not working as expected when L1 is disabled
> ----------------------------------------------------
>
> Key: ISPN-240
> URL: https://jira.jboss.org/jira/browse/ISPN-240
> Project: Infinispan
> Issue Type: Bug
> Components: Distributed Cache
> Affects Versions: 4.0.0.CR1
> Reporter: Galder Zamarreno
> Assignee: Manik Surtani
> Fix For: 4.0.0.CR2
>
>
> The following is what happens when L1 is not enabled for distribution:
> Let's say you call put on 5 keys [k1-k5] on node A of a two node cluster [A,B] and the distribution should be something like: A[k1,k2,k5] and B[k3,k4].
> What really happens is that A *stores all keys* [k1,k2,k3,k4,k5] and B stores [k3,k4]. So, if you now call remove[k1-k5] from B, all the keys in B will be deleted and only the keys that should have belonged to A would be deleted, so the result is that A will still contain [k3,k4].
> With L1, this is not an issue cos whenever there's a write on that key, the L1 is invalidated, so the above test would result on both A and B not containing any keys.
> I'm in the process of replicating this in a smaller unit test. I'm not sure yet what the fix for this would be.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the infinispan-issues
mailing list