This topic has not yet been written. The content below is from the topic description.
Locking In Tree API Understanding when and how locks are acquired when manipulating the tree structure is important in order to maximise the performance of any client application interacting against the tree, while at the same time maintaining consistency. Â Locking on the tree API happens on a per node basis. So, if you're putting or updating a key/value under a particular node, a write lock is acquired for that node. In such case, no write locks are acquired for parent node of the node being modified, and no locks are acquired for children nodes. Â If you're adding or removing a node, the parent is not locked for writing. In JBoss Cache, this behaivour was configurable with the default being that parent was not locked for insertion or removal. Â Finally, when a node is moved, the node that's been moved and any of its children are locked, but also the target node and the new location of the moved node and its children.