[
https://issues.jboss.org/browse/ISPN-3214?page=com.atlassian.jira.plugin....
]
William Burns commented on ISPN-3214:
-------------------------------------
Thinking about adding locking more, there is no way to guarantee consistency and still get
this to work. If we add locking, then there is a time duration between when the local key
would be locked that the owning node could have received an update causing a L1
invalidation. In this case the local node would not run the invalidation since they key
is locked and ignore it. If the local write is conditional and has now failed it will
have the old L1 value from previous. Need to confirm this though.
When non owner updates non-tx dist cache the L1 is not updated
--------------------------------------------------------------
Key: ISPN-3214
URL:
https://issues.jboss.org/browse/ISPN-3214
Project: Infinispan
Issue Type: Bug
Components: Distributed Cache
Affects Versions: 5.2.6.Final
Reporter: William Burns
Assignee: William Burns
Non tx DIST caches only add/update the L1 on a GetKeyValueCommand. The tx DIST cache
updates the L1 cache on write operations as well. This should be consistent and is a
minor performance issue.
--
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