Consistency checker should double check for false possitives
------------------------------------------------------------
Key: JCR-3265
URL: https://issues.apache.org/jira/browse/JCR-3265
Project: Jackrabbit Content Repository
Issue Type: Improvement
Reporter: Unico Hommes
We've experienced that the consistency checker reports false positives when run
in a clustered setup. The reason for this is that the loading in of the node to
be checked and its parent and children is not atomic. First the node is loaded
in and then the parent and children are loaded in subsequently to check whether
they exist and whether they refer back to the node to check. Off course there
is no other way to do this but it does lead to the consistency checker
reporting false positives in this scenario.
It is possible, even quite simple, to virtually eliminate reporting of false
positives by the consistency checker. And it would greatly enhance the
usability of the consistency checker to do so. The solution is to simply double
check the inconsistency when it is detected. We've not seen false positives
being reported since we've implemented this strategy.
Attached is a patch with this solution.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
