Hello @Julia Voskuilen ,
With the Index error you noted, it looks like something is interrupting the index operation that occurs when the issue is transitioning and does not allow the index to complete so the issue on the front end still thinks it is in the old status but on the back end has changed status giving you the follow up errors about the issue being in an invalid state.
First you will want to look into the indexing issue, but after the index issue is corrected you will want to Run the Database Integrity Checker as the very next step to make sure the Index and database are aligned properly and correct the invalid states the issues are stuck in.
The following KB dives into Indexing troubleshooting and would be a good starting point as a referance:
One possibility here mentioned in an info braket at the top of that KB would be an anti virus scanning the index directory while the operation is attempting to complete this can cause a lock on the index while the AV scan is completing:
Indexing speed is not affected by Language Settings. Instead, it relies heavily by the I/O speed of the disk and this could be affected by Antivirus or Virtualised Environment.
Changing the indexing language however play a significant part in the word-stemming and searching.
Check out this KB for Tips on AV configuration:
However in relation to the error, we Usually see this occur in when the applications Index files, most commonly the whole Jira home Directory (the directory where the index lives), gets placed on a NFS mount:
org.apache.lucene.store.AlreadyClosedException: this IndexWriter is closed"
From the support perspective network file systems are not supported (except of NFS for shared home in Data Center) for Server or DC's local home directories (where indexes are stored):
https://confluence.atlassian.com/adminjiraserver/supported-platforms-938846830.html
NFS mounts are supported only for Jira Data Center's shared home directory. They won't work for Server, or DC's local home directory due to Lucene requirements. Read the IndexWriter docs for more information.
If not related to a NFS mount the specifics of the environment will be needed to know for sure what is occuring here so to narrow this one down a bit, Can we get a bit more information about the environment that you are running including the Jira version, is this a Data Center or a standalone install, as well as if the system is configured on an NFS mount?
As an example on the environment variables the Error is more prevelent in Jira versions 8.5 and later due to a change in the Lucene logic. A new version of Lucene shipped with Jira 8.5.x that has additional logic around lock file validation that did not exist in the version of Lucene included in 7.13.x.
For reference, here are the underlying changes in Lucene:
So earlier versions would usually have more Too many Open file errors, compared to the IndexWriter errors. Check out the following KB that has some additional details on diagnosing and fixing the too many open files error that is directly related to this error but Jira version dependent on the related error output:
Let me know what you find
Regards,
Earl
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.