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

Getting a Searcher should not wait for optimise

XMLWordPrintable

      In large instances optimises can take a really long time. Currently getting a searcher will wait for the optimise to complete which will make your instance seem unresponsive. Getting a searcher shouldn't have to wait for an optimize to finish.

            [JRASERVER-20200] Getting a Searcher should not wait for optimise

            crf added a comment - - edited

            The original support case's logs are gone. Based on what is described here and

            • The original case was against 4.0
            • Indexing was significantly reworked in 5.0, including the introduction of the TieredMergePolicy and deprecation of the settings indicated as a workaround
            • In 5.1.6 even the OptimizeIndexJob is shut off

            This issue is apparently no longer applicable.

            crf added a comment - - edited The original support case's logs are gone. Based on what is described here and The original case was against 4.0 Indexing was significantly reworked in 5.0, including the introduction of the TieredMergePolicy and deprecation of the settings indicated as a workaround In 5.1.6 even the OptimizeIndexJob is shut off This issue is apparently no longer applicable.

              cfuller crf
              andreask@atlassian.com Andreas Knecht (Inactive)
              Affected customers:
              1 This affects my team
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: