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 "Francesco Mari (JIRA)" <ji...@apache.org> on 2016/11/22 12:17:59 UTC
[jira] [Commented] (OAK-4957) SegmentRevisionGC MBean should report
more detailed gc status information
[ https://issues.apache.org/jira/browse/OAK-4957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15686581#comment-15686581 ]
Francesco Mari commented on OAK-4957:
-------------------------------------
[~dulceanu], looking at {{org.apache.jackrabbit.oak.plugins.segment.file.FileStoreGCMonitor}}, it seems that {{lastLogMessage}} is never written to. If this is the case, the implementation of {{getLastLogMessage()}} could simply return {{null}}. What do you think? There is no need to rework the patch, I can fix it on the fly if you think it's the case.
> SegmentRevisionGC MBean should report more detailed gc status information
> ---------------------------------------------------------------------------
>
> Key: OAK-4957
> URL: https://issues.apache.org/jira/browse/OAK-4957
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: segment-tar
> Reporter: Michael Dürig
> Assignee: Francesco Mari
> Labels: gc, monitoring
> Fix For: 1.6, 1.5.15
>
> Attachments: OAK-4957-01.patch
>
>
> Regarding this, the current "Status" is showing the last log info. This is useful, but it would also be interesting to expose the real-time status. For monitoring it would be useful to know exactly in which phase we are, e.g. a field showing on of the following:
> - idle
> - estimation
> - compaction
> - compaction-retry-1
> - compaction-retry-2
> - compaction-forcecompact
> - cleanup
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)