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

Reindexing issues with large number of comments, worklogs, history overloads indexers

XMLWordPrintable

      Issue Summary

      This is reproducible on Data Center: yes

      Problem & solution description:
      https://community.developer.atlassian.com/t/safeguards-in-jira-dc-index
      https://community.atlassian.com/t5/Data-Center-articles/Introducing-Safeguards-for-Jira-index/ba-p/2037880#M433
      https://confluence.atlassian.com/jirakb/jira-indexing-limits-stats-1125876330.html

      Steps to Reproduce

      Detailed description:
      https://community.developer.atlassian.com/t/safeguards-in-jira-dc-index/57636/4

      Expected Results

      Index should not be overloaded. Actions on issues with large number of comments, worklogs & history should not affect node & cluster performance & stability.

      Actual Results

      Index is overloaded. When this happens it will affect the performance of all actions triggering re-indexing. Jira may start dropping indexing request which can affect crucial Jira DC components like index replication.

      When the index is overloaded you may see the following exception thrown on failed indexing actions:

      IndexException: Wait attempt timed out - waited  30000 milliseconds

      The problem can be monitored with JIRA-STATS INDEXING-QUEUE logs.

      Workaround

      Archive issues with large number of related entities (comments, worklogs, history).

              mswinarski Maciej Swinarski (Inactive)
              mswinarski Maciej Swinarski (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              19 Start watching this issue

                Created:
                Updated:
                Resolved: