-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
1
-
Problem Definition
During startup Jira will check for index consistency and, if needed, it will recover the index from a recent snapshot.
It will check how far from the database the recently recovered index is (range) and add 24 hours to it.
2024-07-10 19:50:07,718+0000 main INFO [c.a.j.index.ha.DefaultIndexRecoveryManager] [INDEX-FIXER] Re-index start time: {2024-07-10 19:43:21.426}, Latest DB issue-version date: {2024-07-10 19:49:13.738} 2024-07-10 19:50:07,719+0000 main INFO [c.a.j.index.ha.DefaultIndexRecoveryManager] [INDEX-FIXER] Re-indexing issues updated in the last {1 days, 0 hours, 6 minutes, and 46 seconds}. (Note: it's an intentionally wider range)
Suggested Solution
As a Jira administrator I would like to configure how far the index fixer should go in addition to the actual difference between the restored index and the database, instead of having it hardcoded for 24 hours.
- relates to
-
JRASERVER-77906 During Jira startup the index fixer unhelpfully adds a range of 24 hours to catch-up modifications
- Gathering Impact