When is re-indexing required on Jira server

[Eileen Boer]

I'd like to understand when re-indexing is required with a Jira server, and also understand what is getting re-indexed.  It would seem that this wouldn't be something that happens automatically, say when a custom field is changed, but initiated by the administrator? 

Also, what are the impacts to users (of the affected project and other projects) when re-indexing is happening.

If there is documentation on this topic, please feel free to point me to that rather than re-iterating.

Thanks in advance.

[Bryan Trummer - ReleaseTEAM · Accepted solution]

Hi @Eileen Boer - Typically you are prompted to re-index after changes have been made to custom fields or plugins have been updated.  Obviously, we can't all re-index immediately after making a change to one of the previously mention triggers. The following Atlassian link will provide you with the information regarding Indexing in JIRA including the two types or re-indexing (Background and Lock -Down). 

https://confluence.atlassian.com/adminjiraserver0712/search-indexing-959314114.html

[Eileen Boer]

Hi Bryan,

Thanks for the response.  With respect to the linked information and it sounds like

(1) if only one project is using a custom field and has its own unique field configuration scheme, and that field is adjusted, say to add/change a select dropdown option, then only that project will need to be re-indexed. 

(2) background re-indexing will allow users project access, but cause disk fragmentation.  Re-indexing with locks prevents users from accessing a project, will be shorter than background re-indexing, but cause no disk fragmentation.

(3) Both background indexing and indexing with locks can be isolated to a single project if that project is using its own field configuration scheme and its own custom field is the one that has changed.

Does that seem like a fair re-statement?

One last thing: would users of the instance expect to see any sort of slowdown because of the indexing?

[Bryan Trummer - ReleaseTEAM]

Let me answers these to the best of my knowledge.

1. When a custom field is changed it would have to be a system wide index from my understanding. The system would post a notification though when a change prompts for a system wide index rather than the individual index. This documentation here talks a little more about re-index message

https://confluence.atlassian.com/adminjiraserver0712/re-indexing-after-major-configuration-changes-959314121.html

2. Correct.

3. No these are done at the system level. You can run a project re-index which is done under project settings.

Yes, there is some slowdown when doing the background index as its a pretty intense system resource process throwing queries to the DB at a rapid rate. Each instance is different though and the type of slowdown is based on your server configuration, etc.

[Bryan Trummer - ReleaseTEAM]

Hopefully I was able to answer your questions @Eileen Boer. If you found my answer useful, please mark as accepted! Have a great day!

[Eileen Boer]

Hey Bryan,

Before I call this done, I'm searching around for more information on why a custom field only used by one project requires system-level re-indexing.  But haven't found that yet, and would like to understand better why that is.  

[Bryan Trummer - ReleaseTEAM]

Eileen, I don't believe its every time you change a custom field or certain things you change in a custom field prompt the re-index message. Most likely it prompts it when a change is made to a custom field that would effect the searching of that custom field, thus effecting the search index which is system wide. This statement in this document kinda points me towards that.

The above message means that configuration changes have been made to Jira, but have not yet been reflected in the search index. Until Jira's search index has been rebuilt, it is possible that some search queries from Jira will return incorrect results

https://confluence.atlassian.com/adminjiraserver0712/re-indexing-after-major-configuration-changes-959314121.html?_ga=2.75694038.233772939.1545139359-2006550422.1542113441

[Eileen Boer]

Ok thanks Bryan.