Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-62851

Having a huge set of versions causes Boards to break

XMLWordPrintable

      NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.

      Currently, JIRA's default setting for jira.search.maxclauses is 65000. If JIRA has more than this amount in Unrelased Versions, boards will break with this error in the logs:

      2014-03-16 20:03:11,778 http-bio-8080-exec-4 ERROR admin 1263x121x1 1b1c4rs 1.1.1.1.1 /rest/greenhopper/1.0/xboard/work/allData.json [greenhopper.service.issue.IssueDataServiceImpl] A the following query was too complex to generate a query from: {fixVersion in unreleasedVersions()}
      com.atlassian.jira.issue.search.ClauseTooComplexSearchException: A the following query was too complex to generate a query from: {fixVersion in unreleasedVersions()}
              at com.atlassian.jira.jql.query.DefaultLuceneQueryBuilder.createLuceneQuery(DefaultLuceneQueryBuilder.java:43)
              at com.atlassian.jira.issue.search.providers.LuceneSearchProvider.search(LuceneSearchProvider.java:309)
              at com.atlassian.jira.issue.search.providers.LuceneSearchProvider.search(LuceneSearchProvider.java:153)
              at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
              at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
              at sun.reflect.DelegatingMethodAccessorImpl.invoke(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.$Proxy228.search(Unknown Source)
              at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
              at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
              at sun.reflect.DelegatingMethodAccessorImpl.invoke(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.$Proxy228.search(Unknown Source)
              at com.atlassian.greenhopper.service.issue.IssueDataServiceImpl.findImpl(IssueDataServiceImpl.java:166)
              at com.atlassian.greenhopper.service.issue.IssueDataServiceImpl.findWithServiceOutcome(IssueDataServiceImpl.java:48)
              at com.atlassian.greenhopper.web.rapid.work.WorkDataFactory.getWorkDataIssueCountAndLastUpdated(WorkDataFactory.java:234)
              at com.atlassian.greenhopper.web.rapid.work.WorkDataFactory.getAllData(WorkDataFactory.java:141)
              at com.atlassian.greenhopper.web.rapid.work.WorkResource$1.call(WorkResource.java:70)
              at com.atlassian.greenhopper.web.rapid.work.WorkResource$1.call(WorkResource.java:59)
              at com.atlassian.greenhopper.web.util.RestCall.response(RestCall.java:48)
              at com.atlassian.greenhopper.web.AbstractResource.response(AbstractResource.java:60)
              at com.atlassian.greenhopper.web.rapid.work.WorkResource.getPoolData(WorkResource.java:58)
              at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      ...
      

      Workaround

      • Release/archive versions until the system is under the 65000 limit
        or
      • Increase the default limit of 65000, but it is not known how this will affect future performance of the system.
        jira.search.maxclauses = 65000
        

              Unassigned Unassigned
              dchan David Chan
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved: