Details
-
Bug
-
Resolution: Fixed
-
Highest
-
9.1.0, 9.2.0, 9.1.1
-
9.01
-
Severity 2 - Major
-
Description
Issue Summary
This is reproducible on Data Center: yes
Steps to Reproduce
- Make local index lag behind db > 10%. This will switch to getting index from shared.
- When restoring snapshot fails (can be caused by:
JRASERVER-74270) Jira will not fall beck to full reindexing as expected.
Expected Results
When Jira fails to obtain the index from shared it should fall back to doing a full redinex.
https://confluence.atlassian.com/jirakb/index-management-on-jira-start-up-1141500654.html
https://confluence.atlassian.com/jirakb/failed-getting-index-on-start-1141970837.html
//failed step 2
WARN [INDEX-FIXER] ...TODO...
//fall back to step 3
INFO Current node: [NODE-ID]. Triggering full-reindex. Current list of other nodes: [OTHER-NODE-IDS]
INFO Current node: [NODE-ID]. Triggered full-reindex, requestId: {}. Waiting for reindex to finish...
//PROGRESS...
INFO Current node: [NODE-ID]. Full reindex done. Reindex requests processed: []. List of index snapshots available now: [AVAILABLE-SNAPSHOT-NAMES]. Current list of other nodes: [OTHER-NODE-IDS]
Actual Results
The below message is logged in the atlassian-jira.log file:
//failed step 2 WARN [INDEX-FIXER] The duration of time where indices will be missing could not be calculated. Any changes to issues made after the index being restored will not be added to the new index! You can run a background reindex to add missing issue changes to the index.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available