-
Suggestion
-
Resolution: Fixed
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? 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
-
JRACLOUD-2522 two-phase issue reindexing
- Closed
- is related to
-
JRACLOUD-25368 Provide more information before starting a reindex
- Closed
-
JRACLOUD-25788 Re-index : Increase thread number for large instance
- Closed
-
JRACLOUD-36054 Consider modern Lucene concurrency improvements
- Closed
-
JRASERVER-7842 Reindex in background to avoid locking users out
- Closed
- relates to
-
JRACLOUD-10874 Add Re-index as a built-in service
- Closed
[JRACLOUD-7842] Reindex in background to avoid locking users out
Workflow | Original: JAC Suggestion Workflow [ 3154347 ] | New: JAC Suggestion Workflow 3 [ 3645289 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2351180 ] | New: JAC Suggestion Workflow [ 3154347 ] |
Status | Original: Closed [ 6 ] | New: Resolved [ 5 ] |
Component/s | New: Infrastructure & Services [ 46534 ] | |
Component/s | Original: Infrastructure & Services - Indexing [ 46521 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 2109292 ] | New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2351180 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2072740 ] | New: JIRA Bug Workflow w Kanban v6 [ 2109292 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 1866554 ] | New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2072740 ] |
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 Cloud*. Using *JIRA Server*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRASERVER-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 is related to |
Project Import | New: Sat Apr 01 19:36:47 UTC 2017 [ 1491075407146 ] |