Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-10886

SLA configuration changes create indexing pressure on the instance

XMLWordPrintable

      Issue Summary

      When SLA configuration changes all issues in the project may be re-indexed.
      The re-index is done in a heavy way (real-time cross-cluster re-index) and can affect an unlimited number of issues.

      This can cause the whole instance to fail.

      Steps to Reproduce

      1. Create a project with >50K issues on a multinode DC instance 
      2. Change SLA configuration in the project

      Expected Results

      SLAs on the project should be updated and no performance impact

      Actual Results

      A huge number of indexing calls cause high CPU load and slow down the whole instance. Other indexing task may start to timeout (DBR - real time index replication,  NodeReindexService - delayed node index replication/index consistency check, ... any other re-indexing triggered by background, ie. non-http threads). This may cause index inconsistency between nodes which can eventually be only resolved with a full foreground reindex. 

      Workaround

      Currently there is no workaround for the problem.

          Form Name

            [JSDSERVER-10886] SLA configuration changes create indexing pressure on the instance

              bornatowski Bartosz Ornatowski
              kkanojia Kunal Kanojia
              Affected customers:
              3 This affects my team
              Watchers:
              16 Start watching this issue

                Created:
                Updated:
                Resolved: