-
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
- Closed
-
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
[JRASERVER-7842] Reindex in background to avoid locking users out
Workflow | Original: JAC Suggestion Workflow [ 3059158 ] | New: JAC Suggestion Workflow 3 [ 3688512 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: Confluence Workflow - Public Facing v4 [ 2616530 ] | New: JAC Suggestion Workflow [ 3059158 ] |
Workflow | Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2584311 ] | New: Confluence Workflow - Public Facing v4 [ 2616530 ] |
Status | Original: Closed [ 6 ] | New: Resolved [ 5 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2361303 ] | New: JIRA PM Feature Request Workflow v2 - TEMP [ 2584311 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 2128865 ] | New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2361303 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2091779 ] | New: JIRA Bug Workflow w Kanban v6 [ 2128865 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 875555 ] | New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2091779 ] |
Description | Original: 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? |
New:
{panel:bgColor=#e7f4fa} *NOTE:* This suggestion is for *JIRA Server*. Using *JIRA Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRACLOUD-7842]. {panel} 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? |
Link |
New:
This issue relates to |
Component/s | New: Infrastructure & Services - Indexing [ 43408 ] | |
Component/s | Original: Filtering & Indexing [Deprecated] [ 10231 ] |