Details
-
Bug
-
Resolution: Fixed
-
High
-
3.5
-
3.05
-
Description
In certain systems, we've observed that exceptions like:
2006-02-02 10:59:59,462 ERROR [jira.issue.index.DefaultIndexManager] Giving up reindex - waited 10 seconds com.atlassian.jira.issue.index.IndexException at com.atlassian.jira.issue.index.DefaultIndexManager.getIndexLock(DefaultIndexManager.java:463) at com.atlassian.jira.issue.index.DefaultIndexManager.reIndexIssues(DefaultIndexManager.java:239) at com.atlassian.jira.issue.index.DefaultIndexManager.reIndexIssues(DefaultIndexManager.java:211) at com.atlassian.jira.issue.index.DefaultIndexManager.reIndex(DefaultIndexManager.java:391) at com.atlassian.jira.issue.link.DefaultIssueLinkManager.reindexLinkedIssues(DefaultIssueLinkManager.java:70) at com.atlassian.jira.issue.link.DefaultIssueLinkManager.createIssueLink(DefaultIssueLinkManager.java:62) at com.atlassian.jira.web.action.issue.LinkExistingIssue.linkIssue(LinkExistingIssue.java:129) at com.atlassian.jira.web.action.issue.LinkExistingIssue.doExecute(LinkExistingIssue.java:116) at webwork.action.ActionSupport.execute(ActionSupport.java:153)
gets thrown intermittently.
Some investigations are still needed as to exactly why this the case, but initial tests seems to point to the optimise process taking longer than 10s to complete. This means that certain changes might not be reflected in the index, causing the index to be out of date.
Ideally, indexing should occur in the queue, but until then we need to investigate:
- Is it expected that the optimiser may take longer than 10s? Is the time taken relative to the number of total issues? Or issues since last optimisation?
- Is 10s a sensible wait time? Should it be longer?
- Is an optimisation every 150 issues ideal? Will optimisation be faster with fewer issues?
It would also be beneficial if these time outs were configurable.