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 2017/01/26 16:55:24 UTC
[jira] [Deleted] (OAK-5527) leaseUpdateThread might be blocked by
leaseUpdateCheck
[ https://issues.apache.org/jira/browse/OAK-5527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julian Reschke deleted OAK-5527:
--------------------------------
> leaseUpdateThread might be blocked by leaseUpdateCheck
> ------------------------------------------------------
>
> Key: OAK-5527
> URL: https://issues.apache.org/jira/browse/OAK-5527
> Project: Jackrabbit Oak
> Issue Type: Bug
> Reporter: Stefan Eissing
> Assignee: Julian Reschke
> Labels: candidate_oak_1_4
>
> Fighting with cluster nodes losing their lease and shutting down oak-core in a cloud environment. For reasons unknown at this point in time, the whole process seems to skip about two minutes of real time.
> This is a situation from which oak currently does not recover. Code analysis shows that {{ClusterNodeInfo}} is handed the {{LeaseCheckDocumentStoreWrapper}} instance to use as store. This is fatal since any action the {{renewLease()}} tries to do will first invoke the {{performLeaseCheck()}}. The lease check will, when the {{FailureMargin}} is reached, _stall the renewLease() thread_ for 5 retry attempts and then declare the lease to be lost.
> The {{ClusterNodeInfo}} should instead be using the "real" {{DocumentStore}}, not the wrapped one, IMO.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)