Lexorank index timeout when it is running in parallel with Issue indexing

XMLWordPrintable

    • 6.06
    • 7
    • Severity 2 - Major
    • 23

      When Lexorank indexer and Issue indexer working at the same time, the lexorank indexer got a change to throw the following timeout error message

      2015-07-24 06:09:21,201 lexorank-executor-thread-0 DEBUG      [jira.issue.index.DefaultIndexManager] Reindexed 1 issues in 110ms.
      2015-07-24 06:10:28,251 IssueIndexer:thread-3 INFO test 369x199x1 1vn3dw5 127.0.0.1 /secure/admin/IndexReIndex.jspa [action.admin.index.IndexAdminImpl] Re-indexing is 1% complete. Current index: Issue
      2015-07-24 06:10:51,214 lexorank-executor-thread-0 ERROR      [jira.issue.index.DefaultIndexManager] Wait attempt timed out - waited 90000 milliseconds
      com.atlassian.jira.issue.index.IndexException: Wait attempt timed out - waited 90000 milliseconds
      	at com.atlassian.jira.issue.index.DefaultIndexManager.obtain(DefaultIndexManager.java:784)
      	at com.atlassian.jira.issue.index.DefaultIndexManager.access$1100(DefaultIndexManager.java:92)
      	at com.atlassian.jira.issue.index.DefaultIndexManager$IndexLock.tryLock(DefaultIndexManager.java:1142)
      	at com.atlassian.jira.issue.index.DefaultIndexManager.getIndexLock(DefaultIndexManager.java:765)
      	at com.atlassian.jira.issue.index.DefaultIndexManager.reIndexIssues(DefaultIndexManager.java:527)
      	at com.atlassian.jira.issue.index.DefaultIndexManager.reIndexIssues(DefaultIndexManager.java:502)
      	at com.atlassian.jira.issue.index.DefaultIndexManager.reIndexIssues(DefaultIndexManager.java:411)
      	at com.atlassian.jira.issue.index.DefaultIndexManager.reIndexIssueObjects(DefaultIndexManager.java:428)
      	at com.atlassian.jira.issue.index.DefaultIndexManager.reIndex(DefaultIndexManager.java:447)
      	at com.atlassian.jira.issue.index.DefaultIndexManager.reIndex(DefaultIndexManager.java:440)  <+2> (DelegatingMethodAccessorImpl.java:43)
      	at java.lang.reflect.Method.invoke(Method.java:606)
      	at com.atlassian.util.profiling.object.ObjectProfiler.profiledInvoke(ObjectProfiler.java:83)
      	at com.atlassian.jira.config.component.SwitchingInvocationHandler.invoke(SwitchingInvocationHandler.java:28)
      	at com.sun.proxy.$Proxy13.reIndex(Unknown Source)  <+2> (DelegatingMethodAccessorImpl.java:43)
      	at java.lang.reflect.Method.invoke(Method.java:606)
      	at com.atlassian.plugin.osgi.hostcomponents.impl.DefaultComponentRegistrar$ContextClassLoaderSettingInvocationHandler.invoke(DefaultComponentRegistrar.java:129)
      	at com.sun.proxy.$Proxy13.reIndex(Unknown Source)  <+2> (DelegatingMethodAccessorImpl.java:43)
      	at java.lang.reflect.Method.invoke(Method.java:606)
      	at com.atlassian.plugin.osgi.bridge.external.HostComponentFactoryBean$DynamicServiceInvocationHandler.invoke(HostComponentFactoryBean.java:154)
      	at com.sun.proxy.$Proxy13.reIndex(Unknown Source)
      	at com.atlassian.greenhopper.service.IssueIndexServiceImpl.reIndex(IssueIndexServiceImpl.java:60)
      	at com.atlassian.greenhopper.service.IssueIndexServiceImpl.reindexIssueAndSubtasks(IssueIndexServiceImpl.java:135)
      	at com.atlassian.greenhopper.service.lexorank.balance.LexoRankBalancer.balanceFieldId(LexoRankBalancer.java:253)
      	at com.atlassian.greenhopper.service.lexorank.balance.LexoRankBalancer.balanceFieldIds(LexoRankBalancer.java:92)
      	at com.atlassian.greenhopper.service.lexorank.balance.LexoRankScheduledBalanceHandler.run(LexoRankScheduledBalanceHandler.java:48)
      	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
      	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
      	at java.util.concurrent.FutureTask.run(FutureTask.java:166)
      	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
      	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
      	at java.lang.Thread.run(Thread.java:724)
      

      However, once the Issue indexer finished operating, this issue will not appear again. It seems to related to the issue reported in the ticket GHS-11170.

            Assignee:
            Unassigned
            Reporter:
            Yilin (Inactive)
            Votes:
            2 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: