Disable index on other nodes after manual upgrade

[Egidijus Pazikas]

Hello,

Doing an upgrade now and wondering what is best practice or if this idea is good?

Basically, upgraded Jira from 10.5.1 to 10.7.4. First node is up and running, however when starting 2nd (upgraded) node it acquires index lock and starts indexing.

In our environment it can take like 4-5 hours. (3 nodes thats 12 hours)

How to disable this startup index? (via setvenv or jira.properties) so that I can stard other nodes without indexing and then perform full re-index (or use copy index function in jira itself) when all nodes are up and running?

[Shawn Doyle - ReleaseTEAM]

Hi @Egidijus Pazikas 

It's in the startup script the setenv.sh or setenv.bat you can add 

-Dcom.atlassian.jira.startup.rebuild.local.index=false 

To disable the auto reindex at startup.  This is safe to do if you are going to do a full index later.

This doc may shed some light,  https://confluence.atlassian.com/jirakb/index-startup-procedure-in-jira-9-4-and-later-1217301669.html