jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Dürig (JIRA) <j...@apache.org>
Subject [jira] [Commented] (OAK-6836) OnRC report
Date Fri, 15 Dec 2017 08:42:00 GMT

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

Michael Dürig commented on OAK-6836:
------------------------------------

Thanks for the patch. What I'm most concerned about is adding yet another "progress tracking"
mechanism. We already have {{GCListener}}, {{GCMonitor}} and {{GCNodeWriteMonitor}}. I would
rather prefer to route updating of the report through {{GCListener}}. Optimally the reported
would just intercept the methods called on that interface and assemble them into a report.


> OnRC report
> -----------
>
>                 Key: OAK-6836
>                 URL: https://issues.apache.org/jira/browse/OAK-6836
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: segment-tar
>            Reporter: Valentin Olteanu
>            Priority: Minor
>              Labels: production
>         Attachments: gcreport.png
>
>
> Currently, the information regarding an online revision cleanup execution is scattered
across multiple log lines and partially available in the attributes of {{SegmentRevisionGarbageCollection}}
MBean. 
> While useful for debugging, this is hard to grasp for users that need to understand the
full process to be able to read it.
> The idea would be to create a "report" with all the details of an execution and output
it at the end - write to log, but also store it in the MBean, from where it can be consumed
by monitoring and health checks. 
> In the MBean, this would replace the _Last*_ attributes.
> In the logs, this could replace all the intermediary logs (switch them to DEBUG).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message