Uploaded image for project: 'Jackrabbit Oak'
  1. Jackrabbit Oak
  2. OAK-3834

AsyncIndexUpdate default async lease timeout is (too?) long

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: indexing
    • Labels:
      None

      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?

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                thomasm Thomas Mueller
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated: