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

Jira should only re-index once during an upgrade

    XMLWordPrintable

Details

    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

    Description

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      During an upgrade from Jira 3.13.4 to 4.2.2, I couldn't help but notice that issue re-indexing was carried out 4/5 times
      The first re-index is carried out immediately after data import, then a number of upgrade tasks run, 3 or 4 of which carry out issue re-index again.
      Our system has 200,000+ issues in it, and each index job takes approx 90-100 minutes.
      Perhaps all of the re-index jobs are needed, but I can't think of a reason why any more than one re-index would be needed?
      Can Atlassian insert some intelligence into the upgrade process to remove all unnecessary re-index steps?

      Attachments

        Issue Links

          relates to

          Suggestion - JRACLOUD-23468 Jira should only re-index once during an upgrade

          • Closed

          Suggestion - JRASERVER-25122 Optimize the reindexing process when upgrading thru multiple versions of JIRA

          • Closed

          Activity

            People

              Unassigned Unassigned
              b0d88db9bee7 David Corley
              Votes:
              9 Vote for this issue
              Watchers:
              15 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: