Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-14220

Ensure the index optimize operation does not cause index lock timeouts

XMLWordPrintable

    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      In jira-application.properties, we say that JIRA should wait at most 30s to an index lock before giving up:

      # Specified the 'wait time' for a file lock in the Lucene IssueIndexManager (in milliseconds)
# This value should only be modified if you are seeing a jira.issue.index.DefaultIndexManager 'Giving up reindex' ERROR
# in your log files or requested to do so by Atlassian support.
jira.index.lock.waittime=30000

      For an average size JIRA (33k issues) on average hardware, JIRA's nightly index optimization takes 48s. On the ASF JIRA, 75k issues takes 208s. If any write operation takes place during this time it will fail.

      Clearly, 30s hangs are not outside the bounds of possibility. Could we increase this to 300s or something?

              Unassigned Unassigned
              7ee5c68a815f Jeff Turner
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: