-
Suggestion
-
Resolution: Fixed
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
On systems with many issues, a reindex (triggered manually or during an upgrade) implies a potentially large period of downtime. Couldn't JIRA simply build the new index in parallel, and swap it in for the live one when the index is created?
- is duplicated by
-
JRASERVER-2522 two-phase issue reindexing
- Closed
-
JRASERVER-16347 Full reindex without locking Jira - reindex all issues one-by-one?
- Closed
- is related to
-
JRASERVER-15599 Long reindex operations display an impossible completion status
- Closed
-
JRASERVER-25368 Provide more information before starting a reindex
- Closed
-
JRASERVER-25788 Re-index : Increase thread number for large instance
- Closed
-
JRASERVER-36054 Consider modern Lucene concurrency improvements
- Gathering Interest
-
JDEV-27539 Loading...
-
JDEV-29448 Loading...
- relates to
-
JRACLOUD-7842 Reindex in background to avoid locking users out
- Closed
-
JRASERVER-10874 Add Re-index as a built-in service
- Closed