Jira throws No sub-file with id found when indexing
Platform Notice: Data Center - This article applies to Atlassian products on the Data Center platform.
Note that this knowledge base article was created for the Data Center version of the product. Data Center knowledge base articles for non-Data Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Problem
Re-index fails in Jira with a RuntimeIOException error. The following appears in the atlassian-jira.log:
2015-06-18 14:34:23,108 http-bio-8080-exec-19 WARN username 874x357x1 asa6is 192.168.0.10 /secure/QuickCreateIssue.jspa [atlassian.jira.index.AccumulatingResultBuilder] java.io.IOException: No sub-file with id .prx found (files: [.tii, .fnm, .frq, .tis, .fdx, .nrm, .fdt])
com.atlassian.jira.util.RuntimeIOException: java.io.IOException: No sub-file with id .prx found (files: [.tii, .fnm, .frq, .tis, .fdx, .nrm, .fdt])
at com.atlassian.jira.index.WriterWrapper.commit(WriterWrapper.java:147)
at com.atlassian.jira.index.DefaultIndexEngine$WriterReference.commit(DefaultIndexEngine.java:285)
at com.atlassian.jira.index.DefaultIndexEngine$FlushPolicy$2.commit(DefaultIndexEngine.java:78)
at com.atlassian.jira.index.DefaultIndexEngine$FlushPolicy.perform(DefaultIndexEngine.java:148)
at com.atlassian.jira.index.DefaultIndexEngine.write(DefaultIndexEngine.java:217)
at com.atlassian.jira.index.DefaultIndex.perform(DefaultIndex.java:36)
at com.atlassian.jira.index.QueueingIndex$Task.perform(QueueingIndex.java:159)
at com.atlassian.jira.index.QueueingIndex$Task.index(QueueingIndex.java:175)
at com.atlassian.jira.index.QueueingIndex$Task.run(QueueingIndex.java:133)
at java.lang.Thread.run(Unknown Source)
Caused by: java.io.IOException: No sub-file with id .prx found (files: [.tii, .fnm, .frq, .tis, .fdx, .nrm, .fdt])
at org.apache.lucene.index.CompoundFileReader.openInput(CompoundFileReader.java:155)
at org.apache.lucene.index.SegmentCoreReaders.<init>(SegmentCoreReaders.java:88)
at org.apache.lucene.index.SegmentReader.get(SegmentReader.java:114)
at org.apache.lucene.index.IndexWriter$ReaderPool.get(IndexWriter.java:702)
at org.apache.lucene.index.IndexWriter$ReaderPool.get(IndexWriter.java:677)
at org.apache.lucene.index.IndexWriter.doFlush(IndexWriter.java:3571)
at org.apache.lucene.index.IndexWriter.flush(IndexWriter.java:3508)
at org.apache.lucene.index.IndexWriter.prepareCommit(IndexWriter.java:3371)
at org.apache.lucene.index.IndexWriter.commitInternal(IndexWriter.java:3444)
at org.apache.lucene.index.IndexWriter.commit(IndexWriter.java:3426)
at org.apache.lucene.index.IndexWriter.commit(IndexWriter.java:3410)
at com.atlassian.jira.index.WriterWrapper.commit(WriterWrapper.java:143)
Cause
There is a bug in Apache Lucene which is used in Jira for indexing, tracked as part of LUCENE-5541.
You may encounter this when attempting to read from a file without having the necessary permissions or due to a failed network request. As mentioned on JiraSupported Platforms Network storage locations are not supported due to Lucene requirements (such as NFS mounts). Please see the IndexWriter docs for further info.
Resolution
To resolve this problem, the indexes have to be re-built.
- Shutdown Jira.
Copy the contents of the Jira HOME Directory except for the indexes folder.
$JIRA_HOME\caches\indexes- Setting your Jira Home Directory to the server/drive where the install folder is located.
- Restart JIRA.
- Run a full re-index.