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

Details

    Description

      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).

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-66251 Reindexing large number of issues with a lot of change history can cause an OOME

          • Low - Low priority issues
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-45903 Adding a new worklog entry is slow due to a large change history

          • Highest - Our top priority issues
          • Long Term Backlog

          Suggestion - JRASERVER-72612 Limit the number of comments in an issue

          • Closed

          Suggestion - JRASERVER-73167 Ability To Import Issues without Automatic Indexing

          • Gathering Interest
          relates to

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-72045 IndexException: Wait attempt timed out - waited 30000 milliseconds caused by background indexing tasks

          • Highest - Our top priority issues
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-71976 DBR replication Fails on issues with high count of worklog entries

          • Medium - Medium priority issues
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-71980 nodereindex replication fails for single issues with 1000 or more worklog entries

          • Medium - Medium priority issues
          • Closed
          is mentioned by

          IDXREACT-100 Loading...

          mentioned in

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: