As an JIRA Administrator I want check Lucene Index and Issues consistency

Problem Definition

In ATST 1.10.0 the index health check for JIRA was disabled. See JRASERVER-67235

Suggested Solution

Implement Lucene Index status and Issue consistency check

Workaround

• Use REST endpoint: GET <JIRA context>/rest/api/2/index/summary
  • Please see docs for details: https://docs.atlassian.com/jira/REST/7.2.10/#api/2/index/summary

Note on fix

REST APIs:

• GET - /rest/indexanalyzer/1/state?maxResults=10
  • Runs the analysis, this is an expensive call, it will add additional load to DB
• GET - /rest/indexanalyzer/1/statistics
  • Returned if analysis where successfully done

In Jira issue can be in one of 5 different states:

• Index orphan - issue present only in index, should be removed
• DB orphan - issue present only in database, should be added to index
• Outdated issue - if issue in index is not the same as in database
• OK issue - if issues is the same in index and database
• Archived issue - if issue is archived

Example:

{
    "indexOrphans": [
        {
            "issueId": 10101,
            "lastUpdated": 1528706295000
        }
    ],
    "dbOrphans": [
        {
            "issueId": 10306,
            "lastUpdated": 1529308219425
        }
    ],
    "outdatedIssueData": [
        {
            "issueId": 10102,
            "dbLastUpdated": 1528706225000,
            "indexLastUpdated": 1528706405655
        }
    ],
    "okCount": 72,
    "outdatedCount": 1,
    "indexOrphansCount": 1,
    "dbOrphansCount": 1,
    "lastAnalyzeTimestamp": 1529308274757,
    "indexHealth": 97.297295
}

Description:

• indexOrphans, dbOrphans, outdatedIssueData, outdatedCount, indexOrphansCount, dbOrphansCount - see above
• okCount → count of ok issues (from whole Jira)
• lastAnalyzeTimestamp → timestamp when analysis where done
• indexHealth → percentage of issues that or not in index or they are outdated, example: 97.297295 → 97.29% percents of issues in database are ok in index