jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Davide Giannella (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (OAK-3141) Oak should warn when too many ordered child nodes
Date Tue, 04 Jun 2019 15:34:06 GMT

     [ https://issues.apache.org/jira/browse/OAK-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Davide Giannella updated OAK-3141:
    Fix Version/s: 1.16.0

> Oak should warn when too many ordered child nodes
> -------------------------------------------------
>                 Key: OAK-3141
>                 URL: https://issues.apache.org/jira/browse/OAK-3141
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 1.0.16
>            Reporter: Jörg Hoh
>            Assignee: Thomas Mueller
>            Priority: Major
>             Fix For: 1.14.0, 1.16.0
> When working with the RDBMK we came into situations, that large documents did not fit
into the provided db columns, there was an overflow, which caused oak not to persist the change.
We fixed it by increasing the size of the column.
> But it would be nice if Oak could warn if a document exceeds a certain size (for example
2 megabytes); because this warning indicates, that on a JCR level there might be a problematic
situation, for example:
> * ordered node with a large list of childnodes
> * or longstanding sessions with lots of changes, which accumulate to large documents.
> It's certainly nice to know if there's a node/document with such a problem, before the
exceptions actually happens and an operation breaks.
> This message should be a warning, and should contain the JCR path of the node plus the
current size. To avoid that this message is overseen, it would be good if it is written everyonce
in a while (every 10 minutes?) if this condition persists.

This message was sent by Atlassian JIRA

View raw message