-
Suggestion
-
Resolution: Duplicate
-
None
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
when I reindex the database (necessary whenever doing bulk updates via sql), it affects all users in the system at the time – nobody can search while the index is being rebuilt. it would be better/safer to build new indexes in a new location and do a quick swap-out of the old ones, to minimize impact on end-users.
- duplicates
-
JRACLOUD-7842 Reindex in background to avoid locking users out
- Closed
- is related to
-
JRASERVER-2522 two-phase issue reindexing
- Closed
[JRACLOUD-2522] two-phase issue reindexing
Workflow | Original: JAC Suggestion Workflow [ 3154589 ] | New: JAC Suggestion Workflow 3 [ 3656199 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2339824 ] | New: JAC Suggestion Workflow [ 3154589 ] |
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 [ 2103353 ] | New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2339824 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2066017 ] | New: JIRA Bug Workflow w Kanban v6 [ 2103353 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 1828722 ] | New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2066017 ] |
Description | Original: when I reindex the database (necessary whenever doing bulk updates via sql), it affects all users in the system at the time -- nobody can search while the index is being rebuilt. it would be better/safer to build new indexes in a new location and do a quick swap-out of the old ones, to minimize impact on end-users. |
New:
{panel:bgColor=#e7f4fa} *NOTE:* This suggestion is for *JIRA Cloud*. Using *JIRA Server*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRASERVER-2522]. {panel} when I reindex the database (necessary whenever doing bulk updates via sql), it affects all users in the system at the time -- nobody can search while the index is being rebuilt. it would be better/safer to build new indexes in a new location and do a quick swap-out of the old ones, to minimize impact on end-users. |
Link |
New:
This issue is related to |
Project Import | New: Sat Apr 01 19:36:47 UTC 2017 [ 1491075407146 ] |