[jira] [Commented] (OAK-9101) Monitoring for maximum number of entries in biggest map record

["Andrei Dulceanu (Jira)" <ji...@apache.org>]

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

Andrei Dulceanu commented on OAK-9101:
--------------------------------------

[~thomasm], you can find a first attempt to solve this in the patch attached. One thing I was concerned about with this solution: currently the system property records the highest number of entries for a map record in the repository, but there is now way to reset it, provided changes are made to the repository that result in a lower number of maximum entries. I couldn't find a good way to accommodate this. Would it be ok if the property is externally reset?

Could you let me know your thoughts on it?

> Monitoring for maximum number of entries in biggest map record
> --------------------------------------------------------------
>
>                 Key: OAK-9101
>                 URL: https://issues.apache.org/jira/browse/OAK-9101
>             Project: Jackrabbit Oak
>          Issue Type: Task
>          Components: segment-tar
>            Reporter: Andrei Dulceanu
>            Assignee: Andrei Dulceanu
>            Priority: Major
>             Fix For: 1.32.0
>
>         Attachments: OAK-9101.patch
>
>
> With OAK-9095 we introduced logging at different levels when the number of entries in a map record becomes too large. For monitoring purposes, it would be also nice to have a system property (i.e. {{oak.segmentNodeStore.maxMapRecordSize}}) which exposes the maximum number of entries in the biggest map record.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)