How to setup Jira Align Self-Hosted in a multi-node cluster
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
This article describes how to setup a multi-node Jira Align self-hosted instance for a high-availability and to distribute various Jira Align components across multiple nodes
Environment
Jira Align self-hosted
Solution
Reference diagram:
Web Application: To distribute the load across multiple web application servers, only deploy the web application on the front-end nodes using the deploy-only-customer_name.bat. These web application nodes can be load-balanced using session persistence. This prevents user logouts by maintaining the same session with a server without switching the traffic between the nodes.
Connector: The connector service and the Jira services need to maintain a 1:1 relationship. If you need to separate connector services on a standalone node, only install the connector service using the install.bat process.
Back-Office: If the back-office service needs to be deployed on a stand-alone node, install it only using the command-line service installation procedure. To prevent duplicate notifications, there needs to be only one active Back-office server per Jira Align instance.
Was this helpful?