]
William Burns commented on ISPN-1523:
-------------------------------------
This is still the case. All owning nodes keep track of who has requested a given entry.
Currently with both tx and non tx all owners flush the remote L1 caches. We could change
this so only the owning node sends the invalidations, however we would still need to keep
track of all requests on all owning nodes for failover purposes. I am unsure how this
will behave with an update when a rehash occurs though.
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
Affects Versions: 5.1.0.BETA4
Reporter: Dan Berindei
Assignee: William Burns
Priority: Minor
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
For more information on JIRA, see: