[jira] [Updated] (OAK-619) Lock-free MongoMK implementation
[ https://issues.apache.org/jira/browse/OAK-619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger updated OAK-619: - Issue Type: New Feature (was: Bug) > Lock-free MongoMK implementation > > > Key: OAK-619 > URL: https://issues.apache.org/jira/browse/OAK-619 > Project: Jackrabbit Oak > Issue Type: New Feature > 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)
[jira] [Updated] (OAK-619) Lock-free MongoMK implementation
[ https://issues.apache.org/jira/browse/OAK-619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Marth updated OAK-619: -- Fix Version/s: 0.11 > 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)
