[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16752135#comment-16752135 ] Thomas Mueller commented on OAK-7968: - So, active deletion is disabled if the system property "oak.active.deletion.disabled" is set > 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.11.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)
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16737086#comment-16737086 ] Thomas Mueller commented on OAK-7968: - http://svn.apache.org/r1850741 (trunk) > 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 > 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)
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16733149#comment-16733149 ] Thomas Mueller commented on OAK-7968: - [~catholicon] could you have a look at the attached patch [OAK-7968.patch|https://issues.apache.org/jira/secure/attachment/12953650/OAK-7968.patch], would that basically be all that's needed? (Well, this, plus a test, and documentation). > 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 > 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)
