[
https://issues.apache.org/jira/browse/OAK-4859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15529428#comment-15529428
]
Marcel Reutegger edited comment on OAK-4859 at 9/28/16 12:17 PM:
-----------------------------------------------------------------
OAK-4770 introduced a log message at various levels depending on how long a
lease update takes. WARN if it takes more than 10 seconds, INFO if more than 1
second and DEBUG if less than 1 second. Is this what you have in mind?
was (Author: mreutegg):
OAK-4770 introduced a log messages at various levels depending on how long a
lease update takes. WARN if it takes more than 10 seconds, INFO if more than 1
second and DEBUG if less than 1 second. Is this what you have in mind?
> Warn if lease update is invoked with large delay
> ------------------------------------------------
>
> Key: OAK-4859
> URL: https://issues.apache.org/jira/browse/OAK-4859
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: documentmk
> Affects Versions: 1.5.10
> Reporter: Stefan Egli
> Fix For: 1.6
>
>
> DocumentMk's lease mechanism is built on the assumption that the lease is
> periodically updated by each instance. If the update doesn't happen within a
> certain time - and the instance hasn't crashed - there's the risk of the own
> lease to fail. It is therefore important that the lease update happens
> without (large) delay according to the configured period.
> One pattern where this doesn't happen is when the VM is under heavy load due
> to JVM-Full-GC cycles. It seems likely that a memory problem doesn't normally
> happen instantly, but slowly builds up. Based on this assumption we could
> introduce a check that compares the actual time since last lease update with
> the desired period. If these two diverge _a lot_ then we can at least issue a
> log.warn. This might help to easier identify this type of lease failures and
> perhaps find root causes earlier/easier.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
