[infinispan-issues] [JBoss JIRA] (ISPN-2172) Cache removals not removing L1 cached values in non-owners

[Galder Zamarreño (JIRA)]

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

Galder Zamarreño commented on ISPN-2172:
----------------------------------------

Example, k0:

{code}[org.infinispan.interceptors.CallInterceptor] (main:___defaultcache) Executing command: RemoveCommand{key=k0, value=null, flags=null}.
[org.infinispan.interceptors.DistributionInterceptor] (main:___defaultcache) Invoking command RemoveCommand{key=k0, value=null, flags=null} on hosts [NodeA-60583, NodeA-47444]
[org.infinispan.interceptors.DistributionInterceptor] (main:___defaultcache) Put occuring on node, requesting L1 cache invalidation for keys [k0]. Other data owners are [NodeA-47444, NodeA-60583]
[org.infinispan.distribution.L1ManagerImpl] (main:___defaultcache) Invalidating L1 caches for keys [k0]
[org.infinispan.distribution.L1ManagerImpl] (main:___defaultcache) No L1 caches to invalidate{code}

But it's not invalidating NodeB's cache:

{code}java.lang.AssertionError: Key: k0 is present in cache at Cache '___defaultcache'@NodeB-58777{code}
                
> Cache removals not removing L1 cached values in non-owners
> ----------------------------------------------------------
>
>                 Key: ISPN-2172
>                 URL: https://issues.jboss.org/browse/ISPN-2172
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Distributed Cache
>    Affects Versions: 5.1.5.FINAL, 5.2.0.ALPHA2
>            Reporter: Galder Zamarreño
>            Assignee: Galder Zamarreño
>            Priority: Critical
>              Labels: jdg, jdg6
>             Fix For: 5.2.0.ALPHA3, 5.2.0.FINAL
>
>
> There appears to be an issue L1 and removals. 
> Seems like on removal, non-owners are not invalidated and data is left in memory.
> If using a Hot Rod server, it would appear as if the remote get operations don't return anything after removal is cos it goes to an owner node, where data is indeed removed.
> However, if you try to build a test case with embedded cache, it clearly shows that after removal, data is left in memory.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira