-
Bug
-
Resolution: Unresolved
-
Medium
-
None
-
6.4.12, 1000.5.0 Cloud
-
6.04
-
2
-
Severity 2 - Major
-
NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.
Summary
IndexRecoveryLauncher has a problem with timestamps where it will reindex every time even though the logs indicate the timestamp is exactly the same between Lucene and the DB
Steps to Reproduce
1. Restart JIRA
Expected Results
1. A log message will appear with "Latest index date:
{timestamp}, Latest DB date: {timestamp}"
2. With the timestamp being the same no reindex will take place.
Actual Results
1. The timestamps will be the same and then the logs will output "Recover Issue Index - start"
Workaround
There is no workaround as of now
- causes
-
JRASERVER-70248 Jira is trying to do index recovery on invalid issue data coming from Lucene indexes
- Closed
- is duplicated by
-
JRASERVER-62805 IndexRecoveryLauncher reindexes everytime after startup
- Closed
- relates to
-
JRACLOUD-61339 IndexRecoveryLauncher reindexes everytime at startup
- Closed
-
JRASERVER-61595 JIRA start-up message is misleading - You can now access JIRA through your web browser.
- Closed
-
JRASERVER-64233 Recover Issue Index is a blocking and single threaded process (is not a foreground nor background reindex)
- Gathering Impact
- clones
-
JDEV-36964 Loading...
- is cloned by
-
JSEV-436 Loading...