[
https://issues.jboss.org/browse/ISPN-1213?page=com.atlassian.jira.plugin....
]
Manik Surtani commented on ISPN-1213:
-------------------------------------
Hmm, this is a non-trivial problem. Ideally any eviction or expiration code should skip
evicting/expiring nodes which have children, even if these nodes have gone past any
maxIdle or ttl. But implementing this will involve a lot of reinvention of how eviction
works.
What specific use case have you got where you walk the tree rather than peek directly into
an FQN?
TreeCache expires parents that have children
--------------------------------------------
Key: ISPN-1213
URL:
https://issues.jboss.org/browse/ISPN-1213
Project: Infinispan
Issue Type: Bug
Components: Eviction
Affects Versions: 4.2.1.FINAL
Reporter: Todd Ciezadlo
Assignee: Manik Surtani
Fix For: 5.2.0.Final
Attachments: ExpirationTest.java, TreeCacheUtil.java
TreeCache parents expire according to the max-idle value even if they contain children.
This puts the tree cache in an inconsistent state since the "dangling" children
can be retrieved through TreeCache.get(FQN, String) calls, but cannot be traversed to
through TreeCache.getRoot() and Node.getChildren() calls.
Attached unit test to to reproduce.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira