I found the following behaviour of the LRUeviction policy
1) If the node being evicted is a leaf node, whole node is removed.
2) If the node being evicted is a internal node, only the data inside the node is removed. All the childrens of that node remain intact in the tree cache.
Am I right ? or does removal of internal node removes the whole subtree ?
If (2) is correct... then If my application has lots of nodes, then Is there any way to make sure that, at any time, number of nodes (with and without data) in the tree cache is bounded by some pre-configured number ?
You are correct in your statement. Can you configure it such that your children nodes get evicted first?
Please open up a Jira request on JBossCache module. I will think about this.