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

Jira reindex triggered during upgrade doesn't indicate progress in log

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Unresolved
    • None
    • Upgrade
    • 1
    • 1
    • 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.

      Problem Definition

      When carrying out a manual full reindex in JIRA we get this kind of logging in the atlassian-jira.log file:

      2015-11-20 13:19:25,560 IssueIndexer:thread-3 INFO username 760x93x1 6x3ux8 10.155.44.250 /secure/admin/IndexReIndex.jspa [action.admin.index.IndexAdminImpl] Re-indexing is 22% complete. Current index: Issue

      However when doing a JIRA upgrade that requires a full reindex, for example this step:

      2015-11-19 19:04:08,176 localhost-startStop-1 INFO [jira.upgrade.util.BuildNumberDao] Setting current build number to 6318
2015-11-19 19:04:08,192 localhost-startStop-1 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Signalling all data in JIRA should be reindexed. Necessary so stop words are not ignored in exact phrase searches.
2015-11-19 19:04:08,207 localhost-startStop-1 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Signalling all data in JIRA should be reindexed. Necessary so stop words are not ignored in exact phrase searches.' succeeded

      Suggested Solution

      We do not get any feedback in the log as to the progress of the indexing process, there should be some reindex progress logging so that when we carry out upgrades on large instances, we can understand the progress and estimate how long it will take to complete.

      Workaround

      We can increase the indexing logging in the log4j.properties like this:

      log4j.logger.com.atlassian.jira.issue.index = DEBUG, indexlog
log4j.additivity.com.atlassian.jira.issue.index = false

      Which then does provide a full log of each item being indexed, but it still doesn't give any information about the progress of the full index, only which individual tickets have been indexed.

      2015-11-20 12:20:32,546 JiraTaskExectionThread-1 DEBUG anonymous     [jira.issue.index.DefaultIssueDocumentFactory] Indexing issue: ABC-1000
2015-11-20 12:20:32,608 JiraTaskExectionThread-1 DEBUG anonymous     [jira.issue.index.DefaultIssueDocumentFactory] Indexing issue: ABC-1001
2015-11-20 12:20:32,749 JiraTaskExectionThread-1 DEBUG anonymous     [jira.issue.index.DefaultIssueDocumentFactory] Indexing issue: ABC-1002
2015-11-20 12:20:32,842 JiraTaskExectionThread-1 DEBUG anonymous     [jira.issue.index.DefaultIssueDocumentFactory] Indexing issue: ABC-1003
2015-11-20 12:20:32,951 JiraTaskExectionThread-1 DEBUG anonymous     [jira.issue.index.DefaultIssueDocumentFactory] Indexing issue: ABC-1004
2015-11-20 12:20:33,014 JiraTaskExectionThread-1 DEBUG anonymous     [jira.issue.index.DefaultIssueDocumentFactory] Indexing issue: ABC-1005

      Attachments

        Issue Links

          is related to

          Suggestion - JRASERVER-59195 UpgradeTask_Build64001.java should only reindex affected issues

          • Closed

          Suggestion - JRASERVER-59194 Upgrade tasks should trigger foreground reindexing instead of background reindexing

          • Gathering Interest
          relates to

          Suggestion - JRACLOUD-47044 Jira reindex triggered during upgrade doesn't indicate progress in log

          • Closed

          Activity

            People

              Unassigned Unassigned
              d29ac705373a BenjaminW
              Votes:
              2 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated: