-
Suggestion
-
Resolution: Fixed
-
1
-
1
-
Problem
Data Center nodes can ask another node to provide a full index snapshot when:
- A new node is started and has no index
- Index replication has fallen sufficiently far behind
- The copy request has been triggered manually
Currently, this can take upwards of an hour, making the node where the index is broken or missing unusable. The chief contributor to this is the time it takes to zip the index, and this can be shortened by using a faster compression algorithm as long as the I/O device used for shared storage is fast enough.
Suggested fix
- The compression method used can be configured with the jira.index.snapshot.copy.archiver application property.
- Format: jira.index.snapshot.copy.archiver=(snappy|zip|tar)
- setting the jira.index.snapshot.copy.archiver application property to zip will revert to the old behavior.
- causes
-
JRASERVER-68542 Data Center - Reindex snapshot file fails to create if greater than 8GB
- Closed
- has a regression in
-
JRASERVER-68510 DC index copy does not clean up old files when Snappy archiver is used
- Closed
- incorporates
-
JRASERVER-66635 Index Recovery is very slow
- Closed
- mentioned in
-
Page Loading...