Issue Details (XML | Word | Printable)

Key: JRA-9299
Type: New Feature New Feature
Status: Resolved Resolved
Resolution: Fixed
Priority: Critical Critical
Assignee: Chris Mountford [Atlassian]
Reporter: Mark Chaimungkalanont [Atlassian]
Votes: 2
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
JIRA

Add check on startup for Lucene locks that were left behind

Created: 08/Feb/06 07:02 PM   Updated: 23/Jun/06 02:35 AM
Component/s: Backend / Domain Model, Filtering & Indexing
Affects Version/s: 3.5
Fix Version/s: 3.5.2

Time Tracking:
Not Specified

Issue Links:
Reference
 

Participants: Chris Mountford [Atlassian], Donna McGahan [Atlassian], Mark Chaimungkalanont [Atlassian] and Susan Davies
Since last comment: 2 years, 34 weeks, 2 days ago
Resolution Date: 19/Feb/06 10:42 PM
Labels:


 Description  « Hide
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.



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Susan Davies added a comment - 15/Feb/06 09:16 AM
Can you explain how to clear these locks once they're there?

Susan Davies added a comment - 15/Feb/06 09:16 AM
Which file, and where is it located?

Donna McGahan [Atlassian] added a comment - 15/Feb/06 05:29 PM
Susan,

The IOException in the JIRA log will indicate the location of the lock file. For example:

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

The lock file is located in the /usr/prod/jira/atlassian-jira-enterprise-3.4.3-standalone/temp/ directory.

Cheers,
Donna