-
Bug
-
Resolution: Tracked Elsewhere
-
Low
-
None
-
6.4.12
-
6.04
-
2
-
Severity 3 - Minor
-
NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.
Summary
JIRA Indexing health-check checks the state of the search index is consistent with the database. If JIRA Re-index failed for non-issue objects: comments, entities, etc and Lucene index is not consistent, it doesn't report the problem.
Steps to Reproduce
- Run re-index
- While re-indexing running, delete some part of Lucene data: rm -rf jira_6.4/caches/indexes/comments/*cfs
- Wait for Index completes (with errors)
- Run Indexing health-check,
Expected Results
It should report the problem.
Actual Results
It doesn't report the problem. JQL search is not consistent and might lead to Dashboard/filters errors.
Notes
See related https://jira.atlassian.com/browse/JRA-61577
Workaround
Go to Administration > System > Indexing and check if you see error like:
JIRA is unable to perform a background re-index at this time because the index files are either missing or corrupted.
- relates to
-
JRACLOUD-61589 JIRA health-check doesn't report Lucene corruption
- Closed
-
JRASERVER-67235 ATST - remove LuceneSupportHealthCheck as it become obsoleted
- Closed
-
ATST-824 Loading...
- cloned by
-
AHC-52 Loading...