[OAK-3834] AsyncIndexUpdate default async lease timeout is (too?) long

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: indexing
• Epic Link: indexer resilience
• Assignee: Unassigned
• Reporter: Thomas Mueller
• Created: 05/Jan/16 09:56
• Updated: 08/Oct/19 15:21

Description

Oak ensures the async indexes are updated only in one cluster node, using a lease mechanism in oak-core, org.apache.jackrabbit.oak.plugins.index, AsyncIndexUpdate, DEFAULT_ASYNC_TIMEOUT. The default is 15 minutes (system property "oak.async.lease.timeout", default "15").

After killing the process or (when using OSGi) updating the Oak bundle, sometimes the index is not updated for 15 minutes.

15 minutes is quite long. What are the risks of changing this to 1 minutes?

According to some tests, the timeout mechanism is also used with the segment store, even thought there can not be multiple cluster nodes. I thought the timeout mechanism is only used with the document store?

Issue Links

• is related to: OAK-2108 Killing a node may stop async index update to to 30 minutes (Tar storage)
• relates to: OAK-3923 Async indexing delayed by 30 minutes because stop order is incorrect
• relates to: OAK-5893 Async index abort should work even during traversals without index updates