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

Upgrade tasks should trigger foreground reindexing instead of background reindexing

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • None
    • 2
    • 4
    • 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.

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

      Scenario

      Some JIRA upgrade tasks might trigger a background reindexing, for example:

      UpgradeTask_Build64001.java
      private void fixBrokenIssues(List<BrokenIssue> brokenIssues) throws GenericEntityException, IndexException
    {
        for (BrokenIssue brokenIssue : brokenIssues)
        {
            final GenericValue issue = ofBizDelegator.findById("Issue", brokenIssue.issueId);
            if (issue != null)
            {
                issue.set("watches", brokenIssue.correctWatches);
                issue.store();
                issueIndexManager.reIndex(issue);
            }
        }
    }

      JRA-25788 was implemented to utilize more threads for reindexing, but it's only applicable to foreground reindexing. As the upgrade tasks trigger background reindexing, only 1 single thread is used which slows down the whole process.

      Suggestion

      Upgrade tasks should trigger foreground reindexing (where necessary) so that multiple threads can be utilized that speeds up the whole process.

            Unassigned Unassigned
            vdung Andy Nguyen (Inactive)
            Votes:
            6 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated: