Low Issue Summary
When a project with nearly or more than 1,00,000 issues is archived and restored at a later point, a reindex message appears when the project is restored. When click on the "Goto re-index", we see an HTTP 405 error and it takes about a few seconds for the indexing to resume.
This is reproducible on the Data Center: yes
Steps to Reproduce
- Create a project with more than 50,000 issues.
- Under Administration > Projects > Projects select the project and Archive it
- A full-reindexing may or may not be run.
- Goto Administration > Projects > Archived projects and restored the project.
- A popup appears at the top right corner to run a reindex.
- When clicked an HTTP 405 occurs.
- The error gets resolved when a full reindex is run.
Expected Results
The reindex should run successfully after the project is restored with more number of issues.
Actual Results
The below exception is thrown in the atlassian-jira.log file:
ajp-nio-127.0.0.1-8009-exec-95 INFO ADMIN 804x153653x1 24ucxm /rest/api/2/project/ACCRM/restore [jira.issue.managers.DefaultIssueArchiveHelper] Issues in project Access Release Management (ACCRM) have been marked as restored. Issues will not be indexed automatically, so either project or full reindex is required to make issues searchable. Number of restored issues: 160975, time to restore: 113222ms. ajp-nio-127.0.0.1-8009-exec-99 WARN anonymous 815x155000x1 - 10.76.114.79 /status [atlassian.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 ajp-nio-127.0.0.1-8009-exec-99 WARN anonymous 816x155117x2 - 10.76.114.80 /status [atlassian.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 HealthCheck:thread-6 INFO [atlassian.jira.index.DefaultIndexFetcher] [INDEX_FETCHER] Value 192 will be used to determine the max age of usable snapshot for startup in hours. To modify the value please provide system property: com.atlassian.jira.startup.max.age.of.usable.index.snapshot.in.hours. If the property is not set default value: 192 will be used. HealthCheck:thread-6 INFO [atlassian.jira.index.DefaultIndexFetcher] [INDEX_FETCHER] Fresh enough snapshot: IndexSnapshot_11700_231128-010000.tar.sz exists. Jira will try to use it during startup.
Workaround
Currently, the only workaround is to run another full re-indexing