[
https://issues.jboss.org/browse/ISPN-1523?page=com.atlassian.jira.plugin....
]
Pete Muir commented on ISPN-1523:
---------------------------------
When a entry is requested, that can be served by any owner with no notification of the
primary owner. So, when the entry must be invalidated, each owner must invalidate the L1
cache in each node that has requested the key from it.
Unless the notification of the primary owner is changed, this behavior is correct, and so
we can't do this.
Remote nodes send duplicate invalidation messages
-------------------------------------------------
Key: ISPN-1523
URL:
https://issues.jboss.org/browse/ISPN-1523
Project: Infinispan
Issue Type: Enhancement
Components: Distributed Cache
Reporter: Dan Berindei
Assignee: Pete Muir
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