]
William Burns commented on ISPN-1523:
-------------------------------------
And just to clarify this is only true for non-tx caches. In a tx cache only the primary
owner sends the invalidation since it is the one holding the locked key.
{code}
} else if (isL1CacheEnabled && !ctx.isOriginLocal() &&
!ctx.getLockedKeys().isEmpty()) {
// We fall into this block if we are a remote node, happen to be the primary data
owner and have locked keys.
// it is still our responsibility to invalidate L1 caches in the cluster.
blockOnL1FutureIfNeeded(flushL1Caches(ctx));
}
{code}
So we could look into changing non-tx to be the same.
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: