Dear devs,
Recently I dove into some issues that plagued our production systems,
where consistency checks regularly showed that some nodes are not quite as
they should be. Mainly orphaned nodes (nodes no longer being referenced
from their supposed parent), but also missing child nodes (nodes
Hi,
On Fri, Jan 27, 2012 at 9:50 AM, Berry van Halderen
b.vanhalde...@1hippo.com wrote:
Before a JCR save action, the journal table in the database is
consulted. If there are logged actions performed by other Jackrabbit
instances in the cluster than these actions are imported/replayed first
On Fri, Jan 27, 2012 at 11:15 AM, Jukka Zitting jukka.zitt...@gmail.com wrote:
On Fri, Jan 27, 2012 at 9:50 AM, Berry van Halderen
That shouldn't be possible since the first cluster node should be
holding the cluster lock during the entire update-persist operation.
Thus another cluster node
