[
https://issues.apache.org/jira/browse/OAK-440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13500272#comment-13500272
]
Mete Atamel commented on OAK-440:
---------------------------------
I took another look at this today and I think this has to do with lack of
caching in MongoMK. I added a dummy caching implementation in MongoMK and reran
the tests. I got about 20 times improvement. So I opened OAK-445 to implement
some kind of caching in MongoMK.
> Concurrency issue when 3 microkernels are writing in the same db
> ----------------------------------------------------------------
>
> Key: OAK-440
> URL: https://issues.apache.org/jira/browse/OAK-440
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: mongomk
> Environment: linux ubuntu + 1 mongo database instance
> Reporter: Tudor Rogoz
>
> See test ConcurrentWriteMultipleMkMongoTest.testConcurrency().
> org.apache.jackrabbit.mongomk.impl.command.exception.ConflictingCommitException
> on each Thread when 3 mongo microkernels are writing nodes on the same
> database.
> Run the test with: 1000 nodes, 10 nodes for the number of children, and 10
> nodes per commit.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
