[
https://issues.apache.org/jira/browse/OAK-619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger resolved OAK-619.
----------------------------------
Resolution: Fixed
I think this can be resolved now. The lock-free implementation is there and
tests run with the MongoMK.
There are still various open issues around the MongoMK, but it's better to
track them separately.
> Lock-free MongoMK implementation
> --------------------------------
>
> Key: OAK-619
> URL: https://issues.apache.org/jira/browse/OAK-619
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: mongomk
> Reporter: Thomas Mueller
> Assignee: Thomas Mueller
> Fix For: 0.11
>
>
> The current MongoMK implementation has some disadvantages we would like to
> address:
> - some of the collections can't be sharded easily
> - instances synchronize on the "sync" collection
> - concurrent changes to the same node are detected relatively late,
> and merging them requires a re-try
> To address those issues, we will write a prototype of a MongoMK
> implementation that uses a different storage model, that is, only one "nodes"
> collection.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
