[infinispan-issues] [JBoss JIRA] (ISPN-1830) L1: On topology changes lose key requestors information
Mircea Markus (JIRA)
jira-events at lists.jboss.org
Mon Nov 19 05:48:24 EST 2012
[ https://issues.jboss.org/browse/ISPN-1830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mircea Markus updated ISPN-1830:
--------------------------------
Fix Version/s: 5.2.0.CR1
(was: 5.2.0.Beta4)
> L1: On topology changes lose key requestors information
> -------------------------------------------------------
>
> Key: ISPN-1830
> URL: https://issues.jboss.org/browse/ISPN-1830
> Project: Infinispan
> Issue Type: Bug
> Components: Distributed Cache
> Affects Versions: 5.1.0.FINAL
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Blocker
> Fix For: 5.2.0.CR1
>
>
> I think we are losing information about where a key needs to be invalidated when a node changes from owner to non-owner (e.g. because another node joined):
> * We lose the list of requestors stored on this node. Even if all ClusteredGetCommands reached all the current owners (which we are about to change with ISPN-825), once all the current owners leave the new owners will not know about this node's old requestors.
> * We don't add ourselves as a requestor for the key on the new owners when we invalidate the entry and move it to L1.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the infinispan-issues
mailing list