Robert Munteanu created OAK-3152:
------------------------------------
Summary: Stopping/staring a repository in quick succession can
lead to index inconsistencies
Key: OAK-3152
URL: https://issues.apache.org/jira/browse/OAK-3152
Project: Jackrabbit Oak
Issue Type: Bug
Components: mongomk
Affects Versions: 1.3.2
Reporter: Robert Munteanu
I've run into an issue in Apache Sling where locking a node fails ( with a
MultiplexingDocumentStore prototype I'm working on ). Trying to reduce this to
a simple test case in Oak I noticed that I can reproduce the problem with
vanilla Oak as well ( oak trunk as of r1693086 ).
As far as I can tell, the error is a variation on
{noformat}org.apache.jackrabbit.oak.plugins.document.DocumentStoreException:
The node 3:/oak:index/nodetype/:index was already added in revision
r14ed4ddbeb6-0-1, before
r14ed4ddf220-0-2{noformat}
The error I was seeing was with locking, e.g. {noformat}The node
8:/oak:index/jcrLockOwner/:index/admin/var/sling/bundle-content/org.apache.sling.xss
was already added in revision
r14ed49f3814-0-1, before
r14ed4a1da84-0-1{noformat}.
I'll attach a test case which reproduces the error for me with a Mongo-based
DocumentNodeStore.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
