[infinispan-issues] [JBoss JIRA] (ISPN-3214) When non owner updates non-tx dist cache the L1 is not updated

[William Burns (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-3214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12783326#comment-12783326 ] 

William Burns commented on ISPN-3214:
-------------------------------------

Actually looking into this, it would require locking the L1 cache before the remote invocation and after.  This may be okay?  With the changes I have for ISPN-3197, we only update the L1 cache on a read if it is able to acquire the lock immediately.  But this could cause a L1 update to miss if a conditional write occurs and fails since it would no longer update the L1 but held the lock - acceptable?

Also this would be a similar regression to how locking would work in that it would acquire the local lock first before the remote.  But I believe this should be fine since the issue prior was if it acquired the remote owner locks in a different order, causing a deadlock.  Now we only acquire the primary owner lock instead.
                
> 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