[ https://issues.apache.org/jira/browse/OAK-3399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14745175#comment-14745175 ]
Stefan Egli commented on OAK-3399: ---------------------------------- implemented this idea in http://svn.apache.org/r1703137 > 5sec retry loop before declaring lease failure (was: as a last resort try to > update it there) > --------------------------------------------------------------------------------------------- > > Key: OAK-3399 > URL: https://issues.apache.org/jira/browse/OAK-3399 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: core > Affects Versions: 1.3.6 > Reporter: Stefan Egli > Assignee: Stefan Egli > Fix For: 1.3.7 > > > Not sure if this is a good idea - but when the lease check finds out that the > lease is valid for less than the margin (which is 20sec by default), it could > then try to update the lease directly. The 'ugly' part of this is that > normally this job is done by a dedicated background 'lease update' thread - > and now it would be done in the context of a user-thread 'very much under the > hood'. but the advantage would be that it would eg catch the 'laptop-sleep' > situation when running a single vm .. -- This message was sent by Atlassian JIRA (v6.3.4#6332)