[OAK-7968] Active deletion of Lucene binaries: configuration option to disable

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.12.0
• Component/s: indexing, lucene
• Assignee: Thomas Mueller
• Reporter: Thomas Mueller
• Created: 02/Jan/19 10:22
• Updated: 15/Apr/19 09:19
• Resolved: 09/Jan/19 11:17

Description

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).

Issue Links

• is related to: OAK-6950 Active deletion can delete blobs from a shared datastore when a clone setup is created
• is related to: OAK-2808 Active deletion of 'deleted' Lucene index files from DataStore without relying on full scale Blob GC
• is related to: OAK-6862 Active deletion of Lucene binaries: JMX bean, and ability to disable automatic