Details
-
Type:
Suggestion
-
Status: Gathering Interest (View Workflow)
-
Resolution: Unresolved
-
Fix Version/s: None
-
Component/s: Data Center - Index
-
Labels:None
-
Feedback Policy:
Description
Problem Definition
Similar to these existing reports, JRASERVER-47045 and JRASERVER-66204, if a background re-index or project re-index is abruptly stopped due to the node becoming unavailable, it prevents a re-index operation to be run:
A solution was implemented to unlock index jobs, but this only works for foreground re-index: JRASERVER-68616
Suggested Solution
Improve upon the /rest/internal/2/reindex/unlock endpoint to also detect and unlock project and background re-index jobs.
Attachments
Issue Links
- is related to
-
JRASERVER-66204 Bulk Operation can get stuck in JIRA Data Center
-
- Closed
-
- relates to
-
JRASERVER-68616 As an JIRA Datacenter Administrator I want to delete reindexing task from offline node
- Closed