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 "Davide Giannella (JIRA)" <ji...@apache.org> on 2019/04/15 09:20:11 UTC

[jira] [Closed] (OAK-7968) Active deletion of Lucene binaries: configuration option to disable

     [ https://issues.apache.org/jira/browse/OAK-7968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Davide Giannella closed OAK-7968.
---------------------------------

bulk close 1.12.0

> Active deletion of Lucene binaries: configuration option to disable
> -------------------------------------------------------------------
>
>                 Key: OAK-7968
>                 URL: https://issues.apache.org/jira/browse/OAK-7968
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: indexing, lucene
>            Reporter: Thomas Mueller
>            Assignee: Thomas Mueller
>            Priority: Major
>             Fix For: 1.12.0
>
>         Attachments: OAK-7968.patch
>
>
> Active deletion of Lucene binaries (OAK-2808) can be disabled temporarily (OAK-6862), however I don't think there is a simple way to disable it permanently, using a config option (OSGi config / system property). 
> It would be good to have such an option to support the use case where the repository is cloned at runtime, and the clones are started. A workaround is to call the JMX method after startup, but that's a bit inconvenient. It would be best if the config option ensure it's also disabled during startup, even thought it's unlikely that active deletion is scheduled during this startup window (better be on the safe side).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)