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:
Please suggest us the consequences from disabling the Index Optimization Job in JIRA?
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.
In short, upgrade if you have a large JIRA.
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.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
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!
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