[
https://issues.apache.org/jira/browse/OAK-4097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15383852#comment-15383852
]
Michael Dürig commented on OAK-4097:
------------------------------------
I would actually prefer to loop this into {{FileStore.flush()}}. As
{{FileStore}} already has a {{FileStoreMonitor}} member there is no need to
track another dependency. Also this would cover all flushes of the journal
either explicit and implicit by the flush thread. And it does not cover flushes
of the segment buffers alone (i.e. without the journal).
> 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: segment-tar
> Reporter: Chetan Mehrotra
> Assignee: Andrei Dulceanu
> Priority: Minor
> Fix For: 1.6, Segment Tar 0.0.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)
