Details
Description
Summary
Users are able to view, log in and perform actions (Eg. Create issue, search) in JIRA even though a Lock re-index is occurring.
Environment
- JIRA Server 7.4.0
- JIRA Server 7.4.1
Steps to Reproduce
- Perform a Lock re-index on JIRA
- While JIRA performs the re-index, open a new browser window and access JIRA.
- Log in as a different user.
Expected Results
Users are supposed to see a 'JIRA access problem' message only
Actual Results
Users are able to view, access and perform actions in JIRA. If users perform an action during the re-index, the following error below may appear in atlassian-jira.log:
[c.a.j.issue.index.DefaultIndexManager] Wait attempt timed out - waited 30000 milliseconds com.atlassian.jira.issue.index.IndexException: Wait attempt timed out - waited 30000 milliseconds at com.atlassian.jira.issue.index.DefaultIndexManager.obtain(DefaultIndexManager.java:824) at com.atlassian.jira.issue.index.DefaultIndexManager.access$600(DefaultIndexManager.java:90) at com.atlassian.jira.issue.index.DefaultIndexManager$IndexLock.tryLock(DefaultIndexManager.java:1166) at com.atlassian.jira.issue.index.DefaultIndexManager.getIndexLock(DefaultIndexManager.java:810)
Workaround
There is no workaround as of yet.
Attachments
Issue Links
- causes
-
JRASERVER-66670 When a user navigates to JIRA during a foreground re-index, the Johnson page shows a misleading title
- Gathering Impact
- is duplicated by
-
JRASERVER-65944 Lock Reindexing Allows Issue Transition
- Closed
- is blocked by
-
PSR-44 Loading...
- is related to
-
PS-17699 Loading...
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
- was cloned as
-
XPLN-84 Loading...