Health Check: Lucene index files location
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
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
Purpose
About the Health Check
The Lucene index files location health check verifies that your JIRA or Confluence application is not using a Network File System (NFS) mount for the Lucene index files. Indexing in Confluence and JIRA is handled by a third-party library called Lucene, and it does not support NFS mounts.
Impact
Using Lucene over a NFS mount will cause stability issues with the instance. Some of the more common symptoms are slow search speeds (as NFS mounts are typically slower than local) and running out of open files as detailed in the below KBs.
- Confluence: Too many open files error.
- JIRA: Too many open files error in Jira server
For more details about the Lucene restrictions, please refer to the IndexWriter Java documentation on file deletion.
Understanding the Results
Icon | Result | What this means |
|---|---|---|
 | Your lucene search index directory '<index_dir>' is mounted on '<network_mount_type>'. | The application is not using a NFS mount. |
 | Your lucene search index directory '<index_dir>' is mounted on '<network_mount_type>'. You should migrate to a supported network mount. | The application is using a NFS mount, and should be migrated to a local mount. |
Solution
Change the mounting location of the index directory such that it is not mounted over NFS. Only the index directory needs to be mounted locally, it's completely possible to have the application home mounted on NFS except for the lucene dir and this will be acceptable. This can be done with folder mount points.
- For Jira: Search indexing
- For Confluence: Confluence Home and other important directories