[
https://issues.jboss.org/browse/ISPN-1830?page=com.atlassian.jira.plugin....
]
Dan Berindei updated ISPN-1830:
-------------------------------
Summary: L1: On topology changes lose key requestors information (was: L1: On
topology changes we should propagate the key requestors information to the new owners)
Issue Type: Bug (was: Task)
This issue is causing the failures in
https://infinispan.ci.cloudbees.com/job/Infinispan-master-JDK6-tcp-NON_PA...
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
Fix For: 5.2.0.FINAL
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira