[infinispan-issues] [JBoss JIRA] Commented: (ISPN-1341) Eviction treats FIFO as LRU
Jozef Vilkolak (JIRA)
jira-events at lists.jboss.org
Mon Aug 22 03:51:18 EDT 2011
[ https://issues.jboss.org/browse/ISPN-1341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12622378#comment-12622378 ]
Jozef Vilkolak commented on ISPN-1341:
--------------------------------------
Since FIFO is not supported any more it probably should be mentioned in the eviction documentation.
> Eviction treats FIFO as LRU
> ---------------------------
>
> Key: ISPN-1341
> URL: https://issues.jboss.org/browse/ISPN-1341
> Project: Infinispan
> Issue Type: Bug
> Components: Eviction
> Affects Versions: 5.0.0.FINAL
> Reporter: Jozef Vilkolak
> Assignee: Manik Surtani
>
> When a cache is created with eviction strategy set to FIFO it is actually treated as being LRU. This can be seen in org.infinispan.container.DefaultDataContainer.java.
> Functional test for FIFO eviction can be found at [https://svn.devel.redhat.com/repos/jboss-qa/edg/edg-functional-tests/trunk/] in the eviction-strategy module.
> Basically what the test does is insert 3 values into the cache then retrieves the first value(to differentiate FIFO and LRU) and inserts 4th value which sets eviction in motion because of maxEntries=3.
> I would expect the first entered value ("A") to be evicted instead it evicts the second ("B").
> It uses the following cache configuration:
> {code:xml}
> <local-cache
> name="fifo"
> start="EAGER"
> batching="false"
> indexing="NONE">
> <locking
> isolation="REPEATABLE_READ"
> acquire-timeout="20000"
> concurrency-level="500"
> striping="false" />
> <eviction
> strategy="FIFO"
> max-entries="3"
> interval="2000"/>
> </local-cache>
> {code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the infinispan-issues
mailing list