[
https://issues.jboss.org/browse/ISPN-3648?page=com.atlassian.jira.plugin....
]
William Burns commented on ISPN-3648:
-------------------------------------
I can reproduce the issue, however L1 in TX mode has always been invalidated by the owner
node, which in this case just won't work. I will need to think over what I can do for
this. I am guessing we only want to do this invalidation inside the LastChance and leave
the normal L1Interceptor alone.
Inconsistent L1 in tx distributed cache
----------------------------------------
Key: ISPN-3648
URL:
https://issues.jboss.org/browse/ISPN-3648
Project: Infinispan
Issue Type: Bug
Components: Distributed Cache
Affects Versions: 6.0.0.CR1
Reporter: Radim Vansa
Assignee: William Burns
Priority: Critical
Labels: jdg62blocker
In L1LastChance interceptor the CommitCommand sends invalidations only for those keys
whose it is the primary owner. However, some key which is owned in backup way may be read
when the command is replicated and this does not get invalidated after the command
finishes.
This issue is very similar to
https://issues.jboss.org/browse/ISPN-3617
--
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:
http://www.atlassian.com/software/jira