-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Low
-
None
-
Affects Version/s: 10.3.16
-
Component/s: Data Center - Index
-
None
-
10.03
-
1
-
Severity 2 - Major
-
0
Issue Summary
/status check for cluster monitoring renders the Jira nodes unreachable if the index consistency fails.
Steps to Reproduce
- Setup up a Jira instance with considerable amount of data (issues and projects)
- Archive few of the projects such that tolerance percentage (default 10) is breached.
- Archiving issues will remove the issues from the indexes but not from the database and tolerance percent can be breached
Expected Results
Jira nodes should not error out and be accessible to end users
Actual Results
/status check for index consistency renders the search index as inconsistent and node reports the status as ERROR.
The below exception is thrown in the atlassian-jira.log file:
2026-02-18 08:58:22,881+0000 http-nio-8080-exec-9 url: /status WARN anonymous 538x2584x1 1asxvf3 10.229.198.202 /status [c.a.j.issue.index.IndexConsistencyUtils] Index consistency check failed for index 'Issue': expectedCount=1781; actualCount=4888; tolerancePercentage=10, tolerance=178 2026-02-18 08:58:22,881+0000 http-nio-8080-exec-9 url: /status INFO anonymous 538x2584x1 1asxvf3 10.229.198.202 /status [c.a.j.issue.index.DefaultIndexManager] Index consistency check finished. indexConsistent: false; timeToCheckIndexConsistency: 20 ms 2026-02-18 09:00:00,000+0000 Caesium-1-4 INFO anonymous [c.a.j.indexhealer.impl.IndexHealerJobRunner] Running Index Healer scheduled job at: 2026-02-18 09:00:27,887+0000 http-nio-8080-exec-5 url: /status WARN anonymous 540x2609x1 mpqbc8 10.229.198.202 /status [c.a.j.issue.index.IndexConsistencyUtils] Index consistency check failed for index 'Issue': expectedCount=1724; actualCount=669; tolerancePercentage=10, tolerance=172 2026-02-18 09:00:33,526+0000 Caesium-1-4 INFO anonymous [c.a.j.indexhealer.impl.IndexHealerJobRunner] Index Healing batch 4 complete in 13ms. Discovered 88 issues to be healed. Successfully healed: 88. Failed to heal: 0. Remaining 0 to heal. 2026-02-18 09:00:33,552+0000 Caesium-1-4 INFO anonymous [c.a.j.indexhealer.impl.IndexHealerJobRunner] Index Analyzer task finished 2026-02-18 09:01:27,871+0000 http-nio-8080-exec-6 url: /status INFO anonymous 541x2621x1 1780mqo 10.229.198.202 /status [c.a.j.issue.index.DefaultIndexManager] Index consistency check finished. indexConsistent: false; timeToCheckIndexConsistency: 8 ms 2026-02-18 09:01:27,871+0000 http-nio-8080-exec-6 url: /status WARN anonymous 541x2621x1 1780mqo 10.229.198.202 /status [c.a.jira.servlet.ApplicationStateResolverImpl] The search index is inconsistent. This node will report its status as ERROR. You will find information on how to resolve this problem here: https://jira.atlassian.com/browse/JRASERVER-66970
Workaround
- Set the system property -Dcom.atlassian.jira.status.index.check=false so that /status checks are not triggered . Follow these instructions: Setting properties and options on startup.
- Restart Jira and trigger a full reindex to make the indexes consistent
