-
Bug
-
Resolution: Tracked Elsewhere
-
Low (View bug fix roadmap)
-
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 Failed to load
[JRASERVER-61589] JIRA health-check doesn't report Lucene corruption
Minimum Version | New: 6.04 |
Workflow | Original: JAC Bug Workflow v2 [ 2846500 ] | New: JAC Bug Workflow v3 [ 2930904 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Symptom Severity | Original: Minor [ 14432 ] | New: Severity 3 - Minor [ 15832 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2590585 ] | New: JAC Bug Workflow v2 [ 2846500 ] |
Link |
New:
This issue relates to |
Workflow | Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1523366 ] | New: JIRA Bug Workflow w Kanban v7 - Restricted [ 2590585 ] |
Resolution | New: Tracked Elsewhere [ 15 ] | |
Status | Original: Verified [ 10005 ] | New: Resolved [ 5 ] |
Remote Link | New: This issue links to "ATST-824 (Ecosystem JIRA)" [ 333873 ] |
Description |
Original:
h3. 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. h3. 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, h3. Expected Results It should report the problem. h3. Actual Results It doesn't report the problem. JQL search is not consistent and might lead to Dashboard/filters errors. h3. Notes See related https://jira.atlassian.com/browse/JRA-61577 h3.Workaround Go to *Administration* > *System* > *Indexing* and check if you see error like: bq. JIRA is unable to perform a background re-index at this time because the index files are either missing or corrupted. |
New:
{panel:bgColor=#e7f4fa} *NOTE:* This bug report is for *JIRA Server*. Using *JIRA Cloud*? [See the corresponding bug report|http://jira.atlassian.com/browse/JRACLOUD-61589]. {panel} h3. 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. h3. 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, h3. Expected Results It should report the problem. h3. Actual Results It doesn't report the problem. JQL search is not consistent and might lead to Dashboard/filters errors. h3. Notes See related https://jira.atlassian.com/browse/JRA-61577 h3.Workaround Go to *Administration* > *System* > *Indexing* and check if you see error like: bq. JIRA is unable to perform a background re-index at this time because the index files are either missing or corrupted. |
This is now tracked under https://ecosystem.atlassian.net/browse/ATST-824.