[infinispan-issues] [JBoss JIRA] (ISPN-3229) L1 cache entries should not be passivated

[Dan Berindei (JIRA)]

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

Dan Berindei commented on ISPN-3229:
------------------------------------

Actually you can find if an entry is in L1 or not, albeit in more a roundabout way: {{DistributionManager.getLocality(key)}}
If the key is not local, you can assume that it is L1 and it shouldn't be passivated.
                
> L1 cache entries should not be passivated
> -----------------------------------------
>
>                 Key: ISPN-3229
>                 URL: https://issues.jboss.org/browse/ISPN-3229
>             Project: Infinispan
>          Issue Type: Bug
>    Affects Versions: 5.2.6.Final
>            Reporter: William Burns
>            Assignee: Mircea Markus
>         Attachments: DistSyncL1PassivationFuncTest.java
>
>
> L1 entries are stored in the same data container as the real entries.  These can be evicted which is fine, however we don't want them to be passivated as this could be costly to write/read from the cache store.  We should either prevent L1 cache entries from being passivated or have an option to allow for it.
> Currently L1 entries are not differentiated from other entries except through the fact that they are mortal, which is used for other operations as well, which means they would need a placeholder of some kind to tell the container this is a L1 entry.

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