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 "Chetan Mehrotra (JIRA)" <ji...@apache.org> on 2016/03/08 07:03:40 UTC

[jira] [Commented] (OAK-4097) Add metric for FileStore journal writes

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

Chetan Mehrotra commented on OAK-4097:
--------------------------------------

Such a metric can easily be hooked into {{org.apache.jackrabbit.oak.plugins.segment.file.BackgroundThread}} which already collects the timing data. Just need to back them via a metric

> Add metric for FileStore journal writes
> ---------------------------------------
>
>                 Key: OAK-4097
>                 URL: https://issues.apache.org/jira/browse/OAK-4097
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: segmentmk
>            Reporter: Chetan Mehrotra
>            Assignee: Chetan Mehrotra
>            Priority: Minor
>             Fix For: 1.6
>
>
> TarMK flush thread should run every 5 secs and flush the current root head to journal.log. It would be good to have a metric to capture the number of runs per minute
> This would help in confirming if flush is working at expected frequency or delay in acquiring locks is causing some delays



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)