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?
Sounds about right to me. The good news is that this is fixed from 5.0 onwards.
What database are you using?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.