upgrade 4.0 to 4.4.5 took 67 hrs

We are scheduled to upgrade our JIRA instance 4.0 to 4.4.5 .

we tried this in our test environment and it took 67 hrs to complete the whole process.

we have around 2,00,000 issues.

It reindexed several times over the process and on average it took 4.5 hrs for each re-index, it generally takes 1hr 15 min in 4.0

Please suggest any options by which we can reduce this time ? and what could be the reason for the increased reindexing time in 4.4.5?

4 answers

0 vote

Do you have the subversion plugin installed? If you have it and it's connected to a large svn repository, it can churn during upgrades.

Hi, do you see any errors in the logs? I suspect some plugin or error might be causing issues with the re-index process. Is there enough memory? Upgrades usually stress the system and uses more memory.

What database are you using?

0 vote

Sounds about right to me. The good news is that this is fixed from 5.0 onwards.


Suggest an answer

Log in or Join to answer
Community showcase
Louis De Jaeger
Posted Thursday in Off-topic

Friday fun: your best joke

Hi all Lets make this Friday fun really fun and post one (or more) of your best jokes! The joke can be about an Atlassian product, or just a really fun joke you want to share! I’m not the best j...

171 views 12 3
Join discussion

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot