Documentation for JIRA 6.3 EAP developer (EAP) releases only. Not using this? See below:
(JIRA 6.2.x documentation | JIRA OnDemand documentation | earlier versions of JIRA)

Skip to end of metadata
Go to start of metadata

Request for interest

Hi there,

Great to see your interest in Clustering/Load Balancing for JIRA!

Atlassian is looking to build a solution for this to help large Enterprise customers that run JIRA in mission critical environments. At the moment we do not have any artifacts for testing but we are gathering names of interested customers. If you are one of these please, send an email to with the subject: Clustering/Load Balancing and I will respond accordingly.


Kelvin Yap
JIRA Enterprise Advocate

Does JIRA support clustering for scaling?

Not at this time.

However we do understand that customers are interested in how JIRA can scale. To address this we have written a document that explains how JIRA performs in different configurations and it also provides a guide of how to scale JIRA in a large enterprise. So whether you are a new JIRA evaluator that wants to understand how JIRA can scale to your needs, or you're a long time existing JIRA administrator that is interested taking JIRA to the next level we have a document that will point you in the right direction.

To scale JIRA in your organization, there are two key approaches, which can be used in combination to scale JIRA across your entire organization:  

  1. Scaling a single JIRA instance. 
  2. Federation: Using multiple, connected JIRA instances

We detail both techniques to get the most out of JIRA for your organization at our Scaling JIRA guide.

What if I really want JIRA clustering?

Although not supported if this is something you must have then in your environment you may wish to work with one of our Atlassian Experts to come up with a tailor made solution. Please remember that this will not be supported by Atlassian. This means that if you experience a problem that can not be replicated in a non-clustered environment then that is where our support will most likely stop.

Note: If you wish to run JIRA in a clustered environment you will need a license for each node. You can place your order from our secure online order form.

Does JIRA support high-availability?

While not natively supported it is possible to build an environment with a JIRA failover strategy. This best practices guide: Failover for JIRA, assembles some of the best advice from our customers, our partners, and internal staff on setting up a failover solution for JIRA.

  • No labels


  1. Anonymous

    Last we spoke with Wandisco their rep said that they are discontinuing support for their Jira clustering solution.  Scarlet appears to be the only option on the table at this time but is not ready for prime-time.

  2. Wandisco have discontinued the support.

    ----Original Message----
    From: George Powell []

    Unfortunately we no longer offer the JIRA SDK.  If it is just a JIRA solution you are looking for I would recommend speaking with Atlassian for alternative options, however if it is tied in with your usage of Subversion then perhaps there are grounds for further discussion.

    As you are probably aware, WANdisco has the most active core developers from the Subversion project on staff and is a leading provider of enterprise infrastructure software for replication, scalability and high availability.

    By using WANdisco's totally unique replication technology, software development can now occur anywhere without any constraints.  Fortune Global 1000 companies such as BT, Hewlett Packard and Motorola rely on WANdisco's suite of source code management solutions.

    The WANdisco Source Code Management (SCM) suite consists of Subversion MultiSite (WAN Clustering), Subversion Clustering, Subversion Access Control, CVS MultiSite, CVS Clustering and CVS Access Control.

    With our experience of working with customers with large Subversion installations with the JIRAplugin we have experience with the work flows they have implemented to work around such scalability issues that come with JIRA.  If this is something you would like to discuss then please feel to contact me anytime and I looking forward to your response.


    George Powell

    Sales Operations Manager
    WANdisco Inc.

  3. Anonymous

    This is very disturbing that Atlassian does not support HIgh Availability /i Load Balancing ...@ one side 200K issue is the limit and on other end there is no solution to this issue ....

  4. Anonymous

    I hope now, with Enterprise license Atlassian will consider clustering / load balancing of jira. Enterprises don't care about t-shirts

  5. I'm interested in Veritas clustering solution, but there appears to be no clustering agent available for JIRA/ Tomcat. (See here: )

    Veritas supports Oracle WebLogic, but JIRA does not support it.

    Anyone tried/ successfully implemented Veritas clustering?

  6. Anonymous

    Its plainly pathetic that JIRA does not support this ... I have been reading a lot last few days and they keep throwing different links which does not take us anywhere .... JIRA Cli keeps poking its nose all over the place to use as a solution for clustering / syncing etc .... in simple words Atlassian has no solution and customers are left to defend for themselves

  7. Clusters are literally everywhere.

    Either JIRA designed such a way its can't share any data between nodes, or Atlassian doesn't see any benefits in shipping clustered versions (and the reason for that is pretty obvious).

  8. We have a jira 2 node cluster working fine. We use it with pacemaker and drbd. jira is not aware of this and it is an active/passive. If you are on a nix system look at pacemaker/drbd ...if you're on windows then yea you'll probably have a hard time..As for load balancing..Meh I just wanted to share my 2 cents about the clustering part. 

  9. Nice. Can you post any details?

    But JIRA needs load-balancing cluster more than failover one.

    PS Just got a response from Kevin, they finally got something coming (smile)


  10. We discovered that a new feature introduces in JIRA 6.2, the index backups and recovery was implemented in such way that it doesn't work well as a auto-repair functionality, not at all. More details at

    1. Sorin, what do you mean? Only you have access to that JSP

      1. Here is the resulting issue:  JRA-37896 - Index Recovery should have an auto-recover functions when failure happen Open

        use-case: reset your JIRA server. When it will start, there is a chance 95% to have the indexes broken, not the database. JIRA will start but it will be almost useless until an admin will restore the indexes, trigger a background reindexes. That's what I call high-maintenance.