integrity check and indexing

Question

We have the choise of running Background re-index or Lock JIRA and rebuild index. We have discovered that running Background re-index often causes trouble/problems for projects and they often stop working whilst the process is running.

What is Atlassian's advice for this? Is it better for us to perform Re-index project on the actual project that needs it after changes and can this action help us to avoid running a big indexing?

We now run an integrity check first followed by the Lock JIRA alternative to be sure that we do not cause problems for our projects. What is your recommendation?

Helen Ahlberg · Answer

OK - thanks for this very explaining answer

Nic Brough -Adaptavist- · Answer

There's more than two ways of indexing.  It's not quite this simple in reality, but unless you're coding, this is the easiest way to think of it:

* There's a chunk of code which reads the index for an issue.
* There's a chunk of code which reads an issue out of the database and creates a set of index entries for it, based on the "searcher" code for each field and attribute.
* When JIRA needs to index a single issue, it runs the "read index" code above, removes the existing data it finds for that issue from the index, then runs the "create" code for it.
* When you ask JIRA to run a project index, it does a SQL search for "all issues in this project" and runs the create code for each issue.
* When you ask JIRA to run a full background index, it does a SQL for "all issues" and runs the create code for each issue.
* When you ask JIRA to run a full locking index, it throws away the whole index and does a SQL for "all issues" and runs the create code for each issue

Helen Ahlberg · Answer

Can I please check with you what the difference is between these two ways of running indexing?