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

As a Jira Admin I want to configure a tolerate threshold for amount of errors during Jira reindexing

    XMLWordPrintable

Details

    • 5
    • 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

      Problem

      Jira has full reindex process. If any error happends during this time, error is accumulated and showed at the end, eg:

      2018-11-13 10:01:07,436 JiraTaskExectionThread-1 ERROR admin 1139x124894x1 1s 127.0.0.1 /secure/admin/IndexReIndex.jspa [c.a.j.util.index.CompositeIndexLifecycleManager] Reindex All FAILED. Indexer: DefaultIndexManager: paths: [/jira/caches/indexes/comments, /jira/caches/indexes/issues, /jira/caches/indexes/changes, /jira/caches/indexes/worklogs, /jira/caches/indexes/plugins/jira-git-files, /jira/caches/indexes/plugins/jira-git-pullrequestinfos, /jira/caches/indexes/plugins/jira-git-revisions]
com.atlassian.jira.index.IndexingFailureException: Indexing completed with 2 errors
at com.atlassian.jira.index.AccumulatingResultBuilder$CompositeResult.await(AccumulatingResultBuilder.java:150)
...

      In some cases, reindexing process for 3m+ issues might take 20+h and at the same time, number of errors could be quite small (~10) so it's preferable to have non-consistent index then to loose all that accumulated work.
      It could also mitigate problems like JRASERVER-69826

      Suggestion

      • Allow Jira Admin to decide tolerated level of error during reindexing

      Extra

      • Create a tool which will allow to identify missing issues and fix the discrepancy.

      Attachments

        Issue Links

          is related to

          Suggestion - JRASERVER-68483 Improve logging for Jira Lucene reindexing

          • Gathering Interest
          relates to

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-70327 ResultSet Closed when doing a lock and reindex on Jira 8.0+

          • Highest - Our top priority issues
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JSWSERVER-16473 Reindex All FAILED - Caused by null issuenum entry in jiraissue table

          • Low - Low priority issues
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-72688 Reindexing in jira + Postgres frequently fails with : "Cannot change transaction isolation level in the middle of a transaction"

          • Medium - Medium priority issues
          • Gathering Impact

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-77572 Jira full reindex process does not terminate when it encounters a relevant failure

          • Low - Low priority issues
          • Gathering Impact
          mentioned in

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Activity

            People

              Unassigned Unassigned
              ayakovlev@atlassian.com Andriy Yakovlev [Atlassian]
              Votes:
              6 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

                Created:
                Updated: