[
https://issues.apache.org/jira/browse/OAK-535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13565218#comment-13565218
]
Mete Atamel commented on OAK-535:
---------------------------------
Currently, readAndMergeExistingNodes tries to merge nodes between
baseRevisionId and headRevisionId, then nodes/commits are saved and then
saveAndSetHeadRevision tries to detect commits that happened since
nodes/commits are saved and see if they are conflicting. If they are not
conflicting, saveAndSetHeadRevision tries to update the baseRevisionIds and let
things progress (OAK-585). Are you suggesting that we also need to somehow
combine readAndMergeExistingNodes & saveAndSetHeadRevision?
> 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
