JIRA performance issue - Index optimization

[Pratima Gorla]

Hello,

We have JIRA performance issues and we got following error in logs:

com.atlassian.jira.issue.index.IndexException: Wait attempt timed out - waited 18000 milliseconds

So we increased timeout from 18000 to 25000.

But it dint fix out problem. So we are planning to disable the Index Optimization Job in JIRA as per following article:

https://confluence.atlassian.com/display/JIRAKB/How+to+Disable+the+Index+Optimization+Job+in+JIRA.

Please suggest us the consequences from disabling the Index Optimization Job in JIRA?

Thanks!

[Nic Brough -Adaptavist- · Accepted solution]

Disabling index optimisation is essentially "Bad".  For large JIRAs, you will find that performance in some places gradually degrades over time, with restarts not having any effect on it.  It does take a while to begin to be able to measure this effect, but the larger the JIRA install, the more quickly it can happen

Depends on the version though.

• On 5.2 and above, you don't have any options
• On 5.0 and 5.1, disable it by all means.
• Below 5.0, do NOT disable it you have a medium-large JIRA (if you are counting issues in the hundreds of thousands, you need it, even though it falls over).  Your system will gradually begin to lose performance.

In short, upgrade if you have a large JIRA.

[teilor_soares]

Depends of your JIRA version; this job is not necessary from JIRA 5.0 onwards and was deprecated as of JIRA 5.1.6 (https://jira.atlassian.com/browse/JRA-29487), so if you are running newer versions, it should not have any serious consequences.

Cheers!

Teilor

[Pratima Gorla]

Thank you Teilor. We are using JIRA 4.4.5. Thanks!

[Royce Wong]

Hi Teilor, We have the same issue and we are also on JIRA 4.4.5. We increased timeout but the problem keeps coming back. Checked the disk speed and that not the problem either. What are the consequences for disabling Index Optimization in JIRA 4.4.5? Thanks.

[teilor_soares]

DO NOT disable the job if you are running 5.0 versions and below, in large instances this will degrade the performance of the instance at the long run. The best approach would be upgrade your JIRA instance to 6.2 or a newer versions, which has a lot of improvements related to performance.