[
https://issues.apache.org/jira/browse/OAK-535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13565288#comment-13565288
]
Mete Atamel commented on OAK-535:
---------------------------------
Is conflict detection only in readAndMergeExistingNodes enough though? There's
a gap between when nodes/commit are saved and when headRevId is incremented. In
that gap, what if some other MK does some conflicting commits? Wouldn't we need
the same conflict detection that we'd have in readAndMergeExistingNodes at
saveAndSetHeadRevision in order to avoid leaving garbage nodes/commits behind?
> MergeCommand reads complete tree into memory
> --------------------------------------------
>
> Key: OAK-535
> URL: https://issues.apache.org/jira/browse/OAK-535
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: mongomk
> Affects Versions: 0.5
> Reporter: Marcel Reutegger
> Attachments: mergecommandoptimization.patch, mergefixattempt.patch,
> movepatch.diff, moves-in-commit.patch, OAK-535.patch
>
>
> Merging commits to a branch back to head in MongoMK calls MergeCommand, which
> reads the complete tree into memory. The more content is in the repository,
> the longer it takes to store even a simple update as a property change.
--
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
