About Multi-Node Deployments

Last updated: October 21, 2026

Tier Deployment
Enterprise On-Prem

Overview

Note:

Sisense now offers multi-node deployments on Linux cloud native.


Sisense provides flexible design choices for supporting high availability (HA) and scalability for your Sisense deployments. Typically, you want to implement multi-node deployments when you want to optimize performance or build in redundancy. Before implementing a multi-node environment, ask yourself the following questions:

  • Do you want to improve dashboard load time?
  • Do your ElastiCubes take a long time to build?
  • Do you need to support a lot of concurrent users?
  • Do you have many ElastiCubes?
  • Do you need high availability for your system?

If you answered yes to any of these questions, you may want to consider scaling out Sisense.

Multi-node in Linux is achieved using Kubernetes which handles high availability, load balancing, and scaling.

High Availability Requirements

To run the Sisense infrastructure services (MongoDB, RabbitMQ, and ZooKeeper) in high availability, you need at least three nodes that have the Application or Build role.

  • When you install a multi-node deployment with sisense.sh and high_availability: true (the default), MongoDB, RabbitMQ, and ZooKeeper each run three replicas. These replicas can only run on nodes labeled node-<namespace>-Application=true or node-<namespace>-Build=true.

  • Kubernetes spreads the replicas across nodes on a best-effort basis. If fewer than three suitable nodes are available, it still schedules all the replicas, and places more than one replica on the same node. The installation succeeds, but if that node fails, more than one replica of the service is lost.

Which Nodes Run Sisense Services

In a multi-node deployment, the Sisense services that the Helm chart deploys run only on nodes labeled node-<namespace>-Application=true (case-sensitive). A node that has only the Build or Query role does not run these services. When you install with sisense.sh, the installer adds the labels for you, based on the roles in k8s_nodes. When you install with Helm, you label the nodes yourself. See Planning Your Configuration.