jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julian Reschke (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (OAK-4859) Warn if lease update is invoked with large delay
Date Fri, 24 Mar 2017 13:06:41 GMT

     [ https://issues.apache.org/jira/browse/OAK-4859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Julian Reschke updated OAK-4859:
    Labels: candidate_oak_1_0 candidate_oak_1_2  (was: candidate_oak_1_0 candidate_oak_1_2

> 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
>            Assignee: Stefan Egli
>              Labels: candidate_oak_1_0, candidate_oak_1_2
>             Fix For: 1.4.15, 1.5.13, 1.6.0
> 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

View raw message