[
https://issues.apache.org/jira/browse/OAK-3028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14600819#comment-14600819
]
Marcel Reutegger commented on OAK-3028:
---------------------------------------
There is no tool to detect the inconsistency. If the issue occurs, you will see
repeated exceptions about merge failures because of conflicts. E.g.:
{noformat}
org.apache.jackrabbit.oak.plugins.document.DocumentStoreException: The node
11:/oak:index/nodetype/:index/nt%3Aunstructured/test/level-0/level-1/level-2/level-3/level-4/child-0
was already added in revision
r14e2998ce4c-0-1, before
r14e2998f0ab-0-1; document: ...
org.apache.jackrabbit.oak.plugins.document.DocumentStoreException: The node
11:/oak:index/nodetype/:index/nt%3Aunstructured/test/level-0/level-1/level-2/level-3/level-4/child-0
was already added in revision
r14e2998ce4c-0-1, before
r14e29991618-0-1; document: ...
org.apache.jackrabbit.oak.plugins.document.DocumentStoreException: The node
11:/oak:index/nodetype/:index/nt%3Aunstructured/test/level-0/level-1/level-2/level-3/level-4/child-0
was already added in revision
r14e2998ce4c-0-1, before
r14e2999365e-0-1; document: ...
org.apache.jackrabbit.oak.plugins.document.DocumentStoreException: The node
11:/oak:index/nodetype/:index/nt%3Aunstructured/test/level-0/level-1/level-2/level-3/level-4/child-0
was already added in revision
r14e2998ce4c-0-1, before
r14e299959c1-0-1; document: ...
{noformat}
The exceptions will report the same revision when the node was already added.
In the above test run {{r14e2998ce4c-0-1}}, but the revision of the node to be
added will be different with every attempt. In this case you would have to
remove the document directly in the DocumentStore to recover from this
inconsistency.
> Hierarchy conflict detection broken
> -----------------------------------
>
> Key: OAK-3028
> URL: https://issues.apache.org/jira/browse/OAK-3028
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core, mongomk
> Affects Versions: 1.3.0, 1.3.1, 1.0.14, 1.0.15
> Reporter: Marcel Reutegger
> Assignee: Marcel Reutegger
> Priority: Blocker
> Fix For: 1.2.3, 1.3.2, 1.0.16
>
> Attachments: ConcurrentAddRemove2IT.patch
>
>
> Hierarchy conflict detection is broken in 1.0.14. It may happen that a child
> document is created even though the parent is considered deleted.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
