You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Valentin Olteanu (JIRA)" <ji...@apache.org> on 2017/10/16 14:27:00 UTC
[jira] [Commented] (OAK-6836) OnRC report
[ https://issues.apache.org/jira/browse/OAK-6836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16205973#comment-16205973 ]
Valentin Olteanu commented on OAK-6836:
---------------------------------------
[~mduerig], [~frm], [~dulceanu], what do you think about the general idea?
I have some WIP code (independent to segment-tar) that I use to parse the logs and output such reports (I needed it to analyze several days of logs). I could try to adapt the POC to the segment tar and come up with a patch, but I want to know if you think it's worth going this way.
> 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
> Fix For: 1.8
>
>
> 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)