Re-index stuck at 22%, what happens if you restart mid re-index?

[Aprildelay]

Self Hosted, closed network, Jira + JSM.

Re-index stuck at 22%, what happens if you restart mid re-index? We can't proceed with restart unless we know the repercussions. We have a license but are unable to contact support as the only person with an account is OoO.

[Marc -Devoteam-]

Hi @Aprildelay 

A restart should no be an issue, but always, make sure you have a DB backup at hand.

Most likely this is due to resources and probably memory, you probably need to increase the memory that can be used for JIra.

Also see this older community post, https://community.atlassian.com/forums/Jira-questions/Jira-re-indexing-stuck/qaq-p/1785129 

[Aprildelay]

Thank you @Marc -Devoteam- 

For additional context and future community questions, here is the course of events:

1. A new project was added with bulk-cloning, and automations. 
2. A background re-index was initiated while large batch automations were running
3. The re-index stopped at 22%
4. We cancelled the re-index (after 4 days)
5. The re-index says "canceling" still at 22%

We also have noticed poor behaviors related to searches and filtering (not surprising given the re-index is stuck). This also negatively effected BigPicture because (we suspect) it is having trouble finding the queries the Scope is using. 

I'll post a follow up after we do a restart.