[ https://issues.apache.org/jira/browse/OAK-10657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17819626#comment-17819626 ]
Julian Reschke commented on OAK-10657: -------------------------------------- So how do we check this? To check for "own-overwritten-unmerged" we'd (a) have to restrict ourselves to "same" clusterid, and also need to read the commit root, right? > MongoDocumentStore: shrink in-DB documents after updates fail due to 16MB > limit > ------------------------------------------------------------------------------- > > Key: OAK-10657 > URL: https://issues.apache.org/jira/browse/OAK-10657 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: documentmk, mongomk > Reporter: Julian Reschke > Assignee: Julian Reschke > Priority: Major > > To address the 16MB/childorder issue, there are many potential approaches: > - make GC more aggressive > - try to change updates to remove "in-between" changes of ":childOrder" > property > - change the data model of ":childOrder" > - try to shrink document in DB once size related exception happens > This ticket is about the last of these options. > Proposal: > - improve exception thrown by document store so that it can be acted upon > - in document store utils add a method that inspects a document and produces > UpdateOps suitable to shrink the document > - DocumentNodeStore commit could catch exception, obtain update ops, apply > them, and retry once (this should be dependant on a feature toggle) -- This message was sent by Atlassian Jira (v8.20.10#820010)