upgrade 4.0 to 4.4.5 took 67 hrs

santosh reddy May 28, 2012

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 votes
JamieA
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 29, 2012

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

https://jira.atlassian.com/browse/JRA-25122

0 votes
David Corley
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 28, 2012

What database are you using?

0 votes
Harry Chan
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 28, 2012

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.

0 votes
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
August 28, 2012

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.

Suggest an answer

Log in or Sign up to answer