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

["Chetan Mehrotra (JIRA)" <ji...@apache.org>]

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

Chetan Mehrotra commented on OAK-3834:
--------------------------------------

With OAK-5893 now resolved we can lower the timeout value. Probably we can set it to 5 minutes and with that effective timeout would be 5*2 i.e. 10 mins. With this the lease update write would be done every 5 mins

[~catholicon] [~tmueller] Thoughts?

> AsyncIndexUpdate default async lease timeout is (too?) long
> -----------------------------------------------------------
>
>                 Key: OAK-3834
>                 URL: https://issues.apache.org/jira/browse/OAK-3834
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: indexing
>            Reporter: Thomas Mueller
>
> 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?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)