[
https://issues.jboss.org/browse/ISPN-1523?page=com.atlassian.jira.plugin....
]
Mircea Markus commented on ISPN-1523:
-------------------------------------
It's the key owner and not the originator that performs the invalidation:
http://bit.ly/rxyuGN
I think the reason for this is that, with the new smart invalidation logic, the owner
keeps track of the nodes that need invalidated.
So invalidation being initiated by a remote node makes sense.
I'll assign the bug to Pete so that he can confirm and close.
Remote nodes send duplicate invalidation messages
-------------------------------------------------
Key: ISPN-1523
URL:
https://issues.jboss.org/browse/ISPN-1523
Project: Infinispan
Issue Type: Bug
Components: Distributed Cache
Reporter: Dan Berindei
Assignee: Mircea Markus
I though only the originator should send invalidation messages, but I'm seeing these
messages in the log:
{noformat}
2011-11-11 11:10:27,608 TRACE (OOB-2,Infinispan-Cluster,NodeD-8993)
[org.infinispan.interceptors.DistributionInterceptor] Put occuring on node, requesting
cache invalidation for keys [k1]. Origin of command is remote
2011-11-11 11:10:27,608 TRACE (OOB-3,Infinispan-Cluster,NodeA-31187)
[org.infinispan.interceptors.DistributionInterceptor] Put occuring on node, requesting
cache invalidation for keys [k1]. Origin of command is remote
2011-11-11 11:10:27,608 TRACE (OOB-2,Infinispan-Cluster,NodeD-8993)
[org.infinispan.distribution.L1ManagerImpl] Invalidating L1 caches for keys [k1]
2011-11-11 11:10:27,608 TRACE (OOB-3,Infinispan-Cluster,NodeA-31187)
[org.infinispan.distribution.L1ManagerImpl] Invalidating L1 caches for keys [k1]
{noformat}
--
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