How can I reduce full re-index time after upgrade Jira v9? (It tooks almost 57hours.)

[Seonghwa Hong]

Hi there,

The Jira Data Center operated by our company is 8.22.6 version and is clustered into two nodes. Account is used by Crowd. (Jira Licensed users are approximately 1,900 users, All Crowd AD are approximately 80,000 users) And There are about 396,000 issues. 15 plug-ins have been installed, and 3 self-developed plug-ins have been installed and used.
And our server specification is as follows.

DB server:

• 16Cores
  RAM 48GB
  Disk 1,000GB

Jira server:

• 16Cores
  RAM 48GB
  Disk 2,500GB

We were upgraded the Jira in the same copied development environment as the production environment. After upgrade ended, full re-index is worked automatically and I found the log as below when the upgrade is complete.

[c.a.j.issue.index.DefaultIndexManager] ReindexAll took: 206545129 ms in the foreground, index size is 2 GB

Full re-index took almost 57 hours.

Almost all custom field in our Jira use the global field context, so seems to be expensive indexing time as Atlassian documents said. Even so, I wonder if it is normal to take 57 hours. It takes too long.

We going to upgrade Jira at Saturday, but If the reindex takes 57 hours then reindexing is completed early Tuesday dawn, our employee will not be able to use Jira at Monday.

I would like to full reindex without downtime (or less than 30 hours of reindex time) after the version upgrade. Can I copy and use the index directory of the previous backup data? (We have a backup file dated 11th Oct that upgraded version 9 as I said above, and created indexesV2/snapshots directory.)

Is there a good way to reduce the time of re-index? Or let me know if you have any good experiences. Thanks in advance for any help.

[Nic Brough -Adaptavist-]

You will need to contact the admins of that Jira system.

I'm afraid here, we are just end users of Atlassian software.  We have less access to your systems than you do.  

If you're really lucky, one of your admins is here, and will spot this, but it is very rare that happens.