We are moving our JIRA installation (just under 1000 users, about 100K tickets) to Amazon's AWS.
The EC2-instance types being considered (m3.large or m3.xlarge) come with sizeable amounts of "ephemeral storage" – SSD-backed devices, which are fast, but get reset every time the system reboots. We'd like to make good use of these resources and one idea was to place JIRA's indices there.
Reboots are expected to be infrequent (the current server's uptime is something like 500 days) and we can tolerate some delay upon reboot for JIRA to rebuild the indices from scratch. The question is, is the application smart enough to do that automatically, or will an admin have to login and initiate the index-rebuild by hand?
In the former case, will it be useable while indices are being rebuilt – or will it use the "lock everybody out" method? Thank you!
I don't think that would be possible out of the box but you could create a script that triggers the REST API after JIRA has started is a possible way (https://docs.atlassian.com/jira/REST/latest/#d2e4679).
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs