Platform Notice: Server and Data Center Only – This article only applies to Atlassian products on the waiter and data center platforms .
The questions about performance are highly subject on their hardware and besides how much load the server is experiencing while concurrently taking the snapshot. JIRA Uses indexes to provide promptly results to search queries that are made by users and internal functions of JIRA. The Index snapshots provide copies of the holocene state of the Index. These are utilitarian in the event of a fail over scenario so that an offline node can quickly recover .
In the Index Recovery Page, Under Setting, If we enable Index recovery, For the option below, what time/day, it will trigger the snapshot creation:
a. Once per hour: (time?)
b. Once per day: (time?)
c: Once per week: (day? time?)
It will trigger after a moment or two and then at the interval specified, All JIRA services work this room up until JIRA 6.4 where a change is made to allow them to be scheduled more flexibly including at a particular time. In 6.4 we have changed all the services to support proper on schedule and then you can specify what days and times fully .
Can we create the snapshot OnDemand?
There is no specific option for this, see the improvement trace here : JRASERVER-66510 – Getting issue details … STATUS
If we have the index size, 18G, could you estimate how the size for one snapshot?
This is unmanageable to say accurately, but the serve is that an optimize replicate is taken of the index, this will typically be slightly smaller than the original but depends upon many factors like hardware or how a lot cargo the waiter is experiencing at that moment. This compress replicate is then compressed into a nothing archive. We typically see a compaction ration of about 4 or 5 to 1. indeed for 18G, I would estimate about 4G. Your mileage May Vary .
If we have the index size, 18G, Could you estimate how much additional free disk size required for index snapshots?
During taking snapshot, the summons is that an optimize replicate is taken of the index – so this up to 18Gb. This compress imitate is then compressed into a slide fastener archive – 4Gb. JIRA will keep 3 archives. sum : 36Gb of extra release quad ( 2x index size ) .
Please note that transcript of index will be copied to java.io .tmpdir location, by default it ‘s set to
-Djava.io.tmpdir="$CATALINA_TMPDIR", which is set to
CATALINA_TMPDIR="$CATALINA_BASE"/temp which is part of JIRA_INSTALL. If you split JIRA_INSTALL from JIRA_HOME, please make surely that you have adequate quad there .
How can we change the number of index snapshots retained
You can edit the number of backups to retain for the JIRA Index Snapshot Service by following these steps :
- Navigate to System > Indexing (in the Advanced section)
- Make sure that Enable Index Recovery is ON.
- Navigate to System > Services (also in the Advanced section)
- Locate the JIRA Index Snapshot Service and click Edit.
- The first field will be Number of backups to retain, edit this field and click Update.
Can I change the compression method from .tar.sz to zip or tar?
Yes. Starting with Jira 7.12.0, you can choose the compression algorithm that Jira will use to compress the index snapshot file. Please see the play along page : How to change the compression method acting of exponent snapshot files in Jira Data Center
During the snapshot creation, (size=18G), how much time require to generate the snapshot? and will it affect system performance, like slowdown the system, create high load, etc?
At this size the snapshot will take many minutes possibly a long as an hour. How this affects the general organization throughput seems to vary. In our own test we see little impingement, but some customers have reported a significant performance hit. This is an I/O intensive operation and the compression requires both CPU and memory so the affect will depend to a big extent on the capacity of the hardware. Another impact is, that a reindex at the same time as the snapshot creation on the like car will fail due to a compose lock on the index files .
Can we change the snapshot directory to another path?
No. You can use a symbolic Link in a *nix environment. If you map this to a network drive you would need to be careful it did not introduce operation issues.
During the restoration snapshot, it mentions the system will be unavailable, but during a test it was found, that some parts of the system are accessible. Can users work on issue while snapshot restoration?
There is a very short window when the honest-to-god index is swapped out for the one being restored when the exponent is not available and access is not possible. During the major operation of unzipping the snapshot the system will remain available ampere well as during the final examination reconciliation when any issues modified after the snapshot was taken are re-indexed .
And for an instance with 18G index size, how much time needed if perform snapshot restoration?
This is a three-step action :
- The snapshot is unzipped, this will depend on your hardware.
- The current index is swapped out and replaced by the snapshot, this is just a directory rename (move) but should be almost instantaneous.
- Any issues that have been updated since the snapshot was taken will need to be reindexed manually. Typically this would take less time than recovering the whole index. For example, if you have a one week snapshot and your system has 3 years worth of issues, it will take 2% of the time to re-index instead of reindexing a whole 3 years indexes.
|Description||This article goes through frequently asked questions regarding JIRA Indexing Snapshots|