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 "Alex Parvulescu (JIRA)" <ji...@apache.org> on 2016/11/25 08:39:58 UTC
[jira] [Commented] (OAK-5159) Killing the process may stop async
index update to to 30 minutes, for DocumentStore (MongoDB, RDB)
[ https://issues.apache.org/jira/browse/OAK-5159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15695269#comment-15695269 ]
Alex Parvulescu commented on OAK-5159:
--------------------------------------
Could {{Clusterable#getInstanceId}} be used here to figure out if the same instance can grab the lease without waiting?
> Killing the process may stop async index update to to 30 minutes, for DocumentStore (MongoDB, RDB)
> --------------------------------------------------------------------------------------------------
>
> Key: OAK-5159
> URL: https://issues.apache.org/jira/browse/OAK-5159
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: query
> Reporter: Thomas Mueller
> Labels: resilience
> Fix For: 1.8
>
>
> Same as OAK-2108, when using a DocumentStore based repository (MongoDB, RDBMK). This is also a problem in the single-cluster-node case, not just when using multiple cluster node.
> When killing a node that is running the sync index update, then this async index update will not run for up to 15 minutes, because the lease time is set to 15 minutes.
> We could probably use Oak / Sling Discovery to improve the situation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)