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

Add check on startup for Lucene locks that were left behind

    XMLWordPrintable

Details

    • 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.

    Description

      If JIRA is stopped whilst Lucene is reindexing itself, it may leave a lock file behind. This will cause issue indexing to fail on subsequent startups and they will get errors like 

      Caused by: java.io.IOException: Lock obtain timed out: Lock@/usr/prod/jira/atlassian-jira-enterprise-3.4.3-standalone/temp/lucene-9683c976083ae985fecc9c87bdbac47b-commit.lock
	 at org.apache.lucene.store.Lock.obtain(Lock.java:58)
	 at org.apache.lucene.store.Lock$With.run(Lock.java:108)
	 at org.apache.lucene.index.IndexReader.open(IndexReader.java:111)
	 at org.apache.lucene.index.IndexReader.open(IndexReader.java:95)
	 at com.atlassian.jira.util.LuceneUtils.getIndexReader(LuceneUtils.java:31)

      The solution is for the user to stop JIRA, and remove the file before starting JIRA again.

      We should add a Johnson Filter to run this check at startup and give them the appropriate instructions / warning if this occurred.

      Attachments

        Issue Links

          is related to

          Support Request - Issue that is likely specific to the installation JRASERVER-4904 Jira Response Slow

          • Medium - Medium priority issues
          • Closed

          Activity

            People

              chris@atlassian.com Chris Mountford
              mark@atlassian.com MarkC
              Votes:
              2 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: