[jira] [Comment Edited] (OAK-4859) Warn if lease update is invoked with large delay

["Julian Reschke (Jira)" <ji...@apache.org>]

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

Julian Reschke edited comment on OAK-4859 at 8/29/19 11:25 AM:
---------------------------------------------------------------

trunk: (1.5.13) [r1767502|http://svn.apache.org/r1767502]
1.4: (1.4.15) [r1788434|http://svn.apache.org/r1788434]
1.2: (1.2.26) [r1797166|http://svn.apache.org/r1797166]
1.0: (1.0.42) [r1824449|http://svn.apache.org/r1824449]



was (Author: reschke):
trunk: [r1767502|http://svn.apache.org/r1767502]
1.4: [r1788434|http://svn.apache.org/r1788434]
1.2: [r1797166|http://svn.apache.org/r1797166]
1.0: [r1824449|http://svn.apache.org/r1824449]



> 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
>            Priority: Major
>             Fix For: 1.4.15, 1.5.13, 1.6.0, 1.2.26, 1.0.42
>
>         Attachments: OAK-4859-for-1.0.diff
>
>
> 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
(v8.3.2#803003)