[
https://issues.apache.org/jira/browse/OAK-3834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15992505#comment-15992505
]
Thomas Mueller commented on OAK-3834:
-------------------------------------
[~chetanm] [~catholicon] what prevents us from using a 1 minute timeout
(indexing pause at most 2 minutes)? I think 5 minutes timeout (indexing pause
of 10 minutes) is still quite long.
There are two reasons (I know) to use a short timeout:
* Users have to wait until indexes are update.
* Due to caching effect, indexing is probably a bit faster if timeout is
shorter. With caching effect I mean: data that was stored recently is still in
the (MongoDB or filesystem ) cache.
> 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)
