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 "Alex Parvulescu (JIRA)" <ji...@apache.org> on 2016/10/26 09:46:58 UTC
[jira] [Commented] (OAK-4742) Improve FileStoreStatsMBean
[ https://issues.apache.org/jira/browse/OAK-4742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15608010#comment-15608010 ]
Alex Parvulescu commented on OAK-4742:
--------------------------------------
bq. Last gc run / size before gc and after gc / time gc took broken down into the various phases
This is exposed via the {{SegmentRevisionGCMBean}} which delegates to a {{FileStoreGCMonitor}}. Does it still make sense to replicate this info via the {{FileStoreStatsMBean}} too?
> Improve FileStoreStatsMBean
> ---------------------------
>
> Key: OAK-4742
> URL: https://issues.apache.org/jira/browse/OAK-4742
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: segment-tar
> Reporter: Michael Dürig
> Assignee: Michael Dürig
> Labels: monitoring
> Fix For: Segment Tar 0.0.18
>
>
> We should add further data to that MBean (if feasible):
> * Number of commits
> * Number of commits queuing (blocked on the commit semaphore)
> * Percentiles of commit times (exclude queueing time)
> * Percentiles of commit queueing times
> * Last gc run / size before gc and after gc / time gc took broken down into the various phases
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)