[
https://issues.apache.org/jira/browse/OAK-7854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16660238#comment-16660238
]
Michael Dürig commented on OAK-7854:
------------------------------------
I suggest to expose the flush rate via a meter:
[https://github.com/mduerig/jackrabbit-oak/commit/1e8330c9694b82a80448535197bb16062b742f2f]
This commit is based on the
[https://github.com/mduerig/jackrabbit-oak/commits/OAK-7852-2] branch from
OAK-7852. However it would be simple enough to decouple it should we decide on
a different approach there.
[~frm], could you have a look?
> Add liveliness monitoring for FileStore background operations
> ---------------------------------------------------------------
>
> Key: OAK-7854
> URL: https://issues.apache.org/jira/browse/OAK-7854
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: segment-tar
> Reporter: Michael Dürig
> Assignee: Michael Dürig
> Priority: Major
> Fix For: 1.10
>
>
> The FileStore background operations are ultimately executed through a
> {{ScheduledExecutorService}}. In the case this scheduling gets blocked (e.g.
> because of a deadlock or lock contention in one of its tasks) there is chance
> of repository corruption.
> To minimise potential data loss we should implement monitoring endpoints for
> the vital background operations. This would allow deployments to take action
> early in case of failures and thus minimise potential data loss and simplify
> recovery.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
