-
Suggestion
-
Resolution: Unresolved
-
None
-
3
-
1
-
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.
- is related to
-
JRASERVER-68483 Improve logging for Jira Lucene reindexing
- Gathering Interest
- relates to
-
JRASERVER-70327 ResultSet Closed when doing a lock and reindex on Jira 8.0+
- Closed
-
JRASERVER-72688 Reindexing in jira + Postgres frequently fails with : "Cannot change transaction isolation level in the middle of a transaction"
- Closed
-
JSWSERVER-16473 Reindex All FAILED - Caused by null issuenum entry in jiraissue table
- Closed
-
JRASERVER-77572 Jira full reindex process does not terminate when it encounters a relevant failure
- Gathering Impact
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...