How to setup Jira Align Self-Hosted in a multi-node cluster

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:

    (Auto-migrated image: description temporarily unavailable)
  • 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.

Updated on April 15, 2025

Still need help?

The Atlassian Community is here for you.