jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Mueller (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-5159) Killing the process may stop async index update to to 30 minutes, for DocumentStore (MongoDB, RDB)
Date Thu, 16 Nov 2017 08:07:00 GMT

    [ https://issues.apache.org/jira/browse/OAK-5159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16254906#comment-16254906
] 

Thomas Mueller commented on OAK-5159:
-------------------------------------

Not sure if it still such a big problem, now that we have NRT and hybrid indexes.

As far as I understand, still affected is the counter index, and NRT index sizes can grow
large.

[~chetanm] I move it to Oak 1.10, OK?

> 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: indexing
>            Reporter: Thomas Mueller
>              Labels: resilience
>             Fix For: 1.10
>
>
> 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.4.14#64029)

Mime
View raw message