[ 
https://issues.apache.org/jira/browse/OAK-10657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17819633#comment-17819633
 ] 

Stefan Egli edited comment on OAK-10657 at 2/22/24 12:44 PM:
-------------------------------------------------------------

Reading commit root is at least one of the ways, yes. -Unless for example 
DocumentNodeStoreBranch starts to cache branch commit revisions (or something 
along those lines).. there might be some room for optimization perhaps.-  
(scratch that, Branch has all of that already ...) But resolving the commit 
value is the classic approach yes.


was (Author: egli):
Reading commit root is at least one of the ways, yes. Unless for example 
DocumentNodeStoreBranch starts to cache branch commit revisions (or something 
along those lines).. there might be some room for optimization perhaps. But 
resolving the commit value is the classic approach yes.

> 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)

Reply via email to