Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Disabling add-ons during reindex

Florence OConnor December 3, 2019

Hi there,

Our team is currently migrating our Jira server environment to a Linux box. We have around 250000 issues. Once the data was input from our current instance in to the new Linux UAT environment, our team attempted to complete a reindex which showed that it was going to take 48 hours so we stopped the reindex.

After contacting Atlassian, they advised us to disable Scriptrunner and Attachment Checker add-ons and run the reindex again. The reindex then only took 1.5 hours. 

I wanted to know if and what the repercussions may be of completing the reindex this way. 

Any feedback or help would be appreciated.

Thanks,

Florence 

1 answer

Suggest an answer

Log in or Sign up to answer
0 votes
Leonard Chew
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
December 3, 2019

Hi there

If Scriptrunner is making your indexing slow, you are most probably using scripted fields, which are being indexed.
You can turn off the indexing on every scripted field, by setting the searcher to "none".

epicpoints.png

Especially scripted fields that calculate a lot are very expensive in indexing.

By removing the fields from the index, you will not have to disable your add-on when reindexing.

However you will not be able to search the fields anymore. 

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
December 7, 2019

Indeed, because you will have no index for the scripted fields, you won't be able to search on them.

Some of them will gradually creep back into use - after re-enabling ScriptRunner, every time an issue is updated, the scripted fields will be recalculated, and hence go back into search.

This will also happen

If you use the non-locking full index that runs in the background - it will take more than the 48 hours a full index needs, but (hopefully) won't make your system unusable while it is running (test it to see how it performs)

If you re-index a project - also won't stop people using the system and can be prioritised and planned.

Like # people like this
TAGS
AUG Leaders

Atlassian Community Events