Loading...

XML

Word

Printable

Type: Bug
Resolution: Fixed
Priority: Low
Fix Version/s: 9.1.0
Affects Version/s: 7.6.2
Component/s: Data Center - Other, Indexing
Labels:

Introduced in Version:
7.06
Support reference count:
2
Symptom Severity:
Severity 2 - Major
UIS:
1
Bug Fix Policy:
View Atlassian Server bug fix policy

Summary

Index recovery is very slow. This is true of index recovery in all scenarios.

Steps to Reproduce

In AWS CloudFormation, add an additional node
Observe that the index recovery is triggered (Index backup started. Requesting node: <node>)
Observe that index recovery takes >30m to begin, and ~50m to complete

Workaround

Recover the index from a snapshot, or perform a full reindex.

is incorporated by

JRASERVER-67732 Copying index snapshots between Data Center nodes should be faster

Closed

is related to

JRASERVER-66649 Index recovery should use index snapshots first if they are available

Closed

JRASERVER-66550 JIRA Datacenter - Add additional Lucene index checks before propagating index to other nodes

Gathering Interest

is resolved by: ASCI-3 Loading...

mentioned in: Page Loading...; Page Loading...; Page Loading...; Page Loading...

(3 mentioned in)

Assignee:: Maciej Swinarski (Inactive)

Reporter:: Denise Unterwurzacher [Atlassian] (Inactive)

Votes:: 3 Vote for this issue

Watchers:: 10 Start watching this issue

Created:: 16/Jan/2018 11:48 AM

Updated:: 31/May/2023 6:41 PM

Resolved:: 02/Nov/2022 8:48 AM