L1 cache entries should not be passivated ----------------------------------------- Key: ISPN-3229 URL: https://issues.jboss.org/browse/ISPN-3229 Project: Infinispan Issue Type: Bug Security Level: Public(Everyone can see) Components: L1 Affects Versions: 5.2.6.Final Reporter: William Burns Assignee: William Burns Fix For: 7.0.0.Beta2 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.