Index corruption can be caused by all sorts of things, and the only way you're going to find it is by investigation and monitoring.
The first thing to do though is a full, locking, re-index. This will recreate the index from scratch, giving you a clean, uncorrupted index. If the damage was done by upgrade, migration or a crash of some sort, then this will fix the files and the error should vanish.
However, if it was caused by something else, it's going to keep happening. There are a multitude of things that could cause it, but you'll need to look for the thing that is doing a "bad" write to the index.
Some causes include:
- Disk is full when Jira is trying to write to the index
- You've put the index on the wrong type of file system
- You've removed one of the standard built-in post-functions on a transition
- You've got a script or app that doesn't index issues properly when it should
- You have written data to the database with SQL instead of going through Jira
But, that list is only a starting point.
First, I would search the log for other indexing errors, but if you do not find any, you will need to start looking at configurations and looking at when the corruption happens so you can tie it to a particular process.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.