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

Optimizing index during intensive work causes problems

      Sometimes JIRA writes in log:
      INFO [jira.issue.index.DefaultIndexManager] Optimising the index because 4000 issues have been re-indexed since
      last optimise. Threshold is 4000.
      After that it's locks indexes and overall performance. It takes about 1,5 minutes, during which we have average 5-6 updates (sometimes 10-15). All this updates are finished with IndexException. The result is outdated indexes for all failed operations (Issue navigator values don't corresponds to real state of Issues)

            [JRASERVER-16277] Optimizing index during intensive work causes problems

            AntonA added a comment -

            Hi Andrey,

            This will be addressed in JIRA 4.0 by JRA-15549.

            For the time being you can increase the value of jira.index.max.reindexes in the jira-application.properties to a larger number.

            JIRA will need to be restarted to pick up this change.

            Cheers,
            Anton

            AntonA added a comment - Hi Andrey, This will be addressed in JIRA 4.0 by JRA-15549 . For the time being you can increase the value of jira.index.max.reindexes in the jira-application.properties to a larger number. JIRA will need to be restarted to pick up this change. Cheers, Anton

              Unassigned Unassigned
              2d15ef7ea19e Andrey Larionov
              Affected customers:
              0 This affects my team
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: