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 "Thomas Mueller (JIRA)" <ji...@apache.org> on 2014/06/25 09:02:24 UTC

[jira] [Commented] (OAK-1912) The UUID index temporarily not available during Oak upgrade

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

Thomas Mueller commented on OAK-1912:
-------------------------------------

As a workaround: before the upgrade, the limit for long running queries could be set (manually over JMX). This will make those queries fail. At least they would not traverse the whole repository. The limit could then be reset after the upgrade.

> The UUID index temporarily not available during Oak upgrade
> -----------------------------------------------------------
>
>                 Key: OAK-1912
>                 URL: https://issues.apache.org/jira/browse/OAK-1912
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: query
>    Affects Versions: 1.0, 1.0.1
>            Reporter: Thomas Mueller
>
> In an OSGi framework, when upgrading the Oak version, the UUID index is temporarily not available, but queries with the condition "uuid=<x>" are still run, and therefore traverse the whole repository.
> This makes upgrading the Oak version very slow.
> I guess the problem is that the old index is stopped before the rest of oak-core is stopped, or the new index is started after the rest of oak-core is started.



--
This message was sent by Atlassian JIRA
(v6.2#6252)