[ https://issues.apache.org/jira/browse/OAK-4859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Egli resolved OAK-4859. ------------------------------ Resolution: Fixed Assignee: Stefan Egli Fix Version/s: (was: 1.6) 1.5.13 Implemented a log.warn if time between 2 {{renewClusterIdLease}} calls is longer than 5 sec: http://svn.apache.org/viewvc?rev=1767502&view=rev > 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 > Fix For: 1.5.13 > > > 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)