[infinispan-issues] [JBoss JIRA] (ISPN-3273) Dist L1 owners that aren't primary don't respect assumeOriginKeptEntryInL1

[William Burns (JIRA)]

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

William Burns commented on ISPN-3273:
-------------------------------------

This issue is caused due to assumeOriginKeptEntryInL1 only confirms with the origin in the ctx.  In the case of DIST the primary owner is contacted first by the calling node.  The primary owner than forwards the update to the other owner nodes.  The other owner nodes think the call was therefore started by the primary node and thus will invalidate all known requestors for the given key.  Currently there is no way to fake what the origin is so the other owners would know which node not to send to.
                
> Dist L1 owners that aren't primary don't respect assumeOriginKeptEntryInL1
> --------------------------------------------------------------------------
>
>                 Key: ISPN-3273
>                 URL: https://issues.jboss.org/browse/ISPN-3273
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Distributed Cache
>            Reporter: William Burns
>            Assignee: William Burns
>         Attachments: DistSyncFuncTest.java
>
>
> When a write operation occurs causing a L1 invalidation, there is a boolean to say assumeOriginKeptEntryInL1 which means the owner won't send an invalidation to the originating node that caused this update.  This works fine for the primary owner, however any additional backups think the origin is the primary owner and such send invalidations to possibly the real origin.
> This affects both tx and non tx caches.  Tx caches that are sync don't see the problem since locking prevents the invalidation, however it causes an unneeded network roundtrip which can cause delay.

--
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