Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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.

Thanks,

Florence 

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

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. 

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 Leonard Chew likes this

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase

The benefits of using Jira in different departments

Jira is a great tool to use across different departments. Forget that paperwork – switch to Jira and get that tasks done smoothly. Marketing Jira allows for a complete digital transformation of you...

101 views 0 6
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you