You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Julian Reschke (Jira)" <ji...@apache.org> on 2019/11/15 12:33:00 UTC
[jira] [Comment Edited] (OAK-4739) lease: immediate renew after
long renew call
[ https://issues.apache.org/jira/browse/OAK-4739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15455148#comment-15455148 ]
Julian Reschke edited comment on OAK-4739 at 11/15/19 12:32 PM:
----------------------------------------------------------------
Right. Without having a DocumentStore API to specify the timeout, and assuming a global change for all operations might be the wrong things to do -- maybe we should run the update in a separate thread and abort it when it takes too long?
was (Author: reschke):
Right. Without having a DocumentStore API to specify the timeout, and assuming a gloval change for all operations might be the wrong things to do -- maybe we should run the update in a separate thread and abort it when it takes too long?
> lease: immediate renew after long renew call
> --------------------------------------------
>
> Key: OAK-4739
> URL: https://issues.apache.org/jira/browse/OAK-4739
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: documentmk
> Affects Versions: 1.5.8
> Reporter: Martin Böttcher
> Priority: Major
> Labels: resilience
>
> A single temporary network issue can shut down the DocumentStore. We observed the following situation:
> # org.apache.jackrabbit.oak.plugins.document.ClusterNodeInfo.renewLease was called (this is done regularly and completely normal)
> # the network had a temporary issue (whatsoever)
> # the database call terminated after a lot of time (the default db maxWaitTime is 120 seconds).
> # org.apache.jackrabbit.oak.plugins.document.ClusterNodeInfo.renewLease decides that the current lease is too old (>120 seconds thats the default for the oak.documentMK.leaseDurationSeconds property), sets a leaseCheckFailed variable and throws an Exception
> # because leaseCheckFailed is set all following tries (if any) will immediately throw an Exception, too.
> I'd recommend to make the ClusterNodeInfo code more robust so that at least one retry will be made.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)