We need some advice regarding the indexation of JIRA in case we use master and slave configuration. Indexing JIRA in slave mode can take lot of time and makes JIRA unavailable for users, so we need to know if there is a way to avoid this unavailability. We thought about some ideas: create a folder shared between JIRA master and slave.
Any proposition is welcome.
Thanks for your help!
This isn't going to be easy. Despite charge the new Enterprise licences for Jira, it still doesn't come with basic Enterprise features. if you create a shared folder between the two instances and only have one running at a time you may get it to work but the problem is you can't have two instances access the lucine index at once as they will lead to corruption. This is the main problem with trying to get a Jira cluster, attachments are fine but everything in Jira runs off the index which is why it's unavailable during a re-index. There is a distributed version of Lucene available but for some reason Atlassian haven't made any moves to using it.
Even if you got to Atlassian, they will tell you to get a bigger server that can handle the load & use a cold standby for failover.
I presume you've already read this?
On this topic: Atlassian has just released a dedicated best practice guide for High Availability. It covers a cold failover scenario and includes implementation details on reverse proxying, monitoring, replication and failover mechanisms:
On July 9, 2014, Atlassian has released its Enterprise Edition which answers all the questions about JIRA Load Balancing and Clustering. It is available only from JIRA 6.3. Upgrade soon and enjoy clustered JIRA.
More info can be found in:
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot