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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Disabling add-ons during reindex

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.



1 answer

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".


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. 

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

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events