HA Cluster Configuration

Copyright © TigerGraph. All Rights Reserved.

A TigerGraph system with High Availability (HA) is a cluster of server machines which uses replication to provide continuous service when one or more servers are not available or when some service components fail. TigerGraph HA service provides loading balancing when all components are operational, as well as automatic failover in the event of a service disruption. One TigerGraph server consists of several components (e.g., GSE, GPE, RESTPP). The default HA configuration has a replication factor of 2, meaning that a fully-functioning system maintains two copies of the data, stored on separate machines. Replication factor of 2 is the minimum to support HA configuration. Users can choose to set a higher replication factor depending on their requirements.

System Requirements

  • An HA cluster needs at least 3 server machines . Machines can be physical or virtual. This is true even the system only has one graph partition.

  • For a distributed system with N partitions (where N > 1), the system must have at least 2N machines.

  • The same version of the TigerGraph software package is installed on each machine.


Starting from version 3.0, configuring a HA cluster is part of Platform installation, please check the document TigerGraph Platform Installation Guide for detail.

Install TigerGraph

Follow the instructions in the document TigerGraph Platform Installation Guide to install the TigerGraph system in your cluster.

HA configuration can only be done at the time of system installation and before deploying the system for database use. HA configuration change after installation is not supported. Converting a non-HA system to an HA cluster would require reinstalling all the TigerGraph components and rebuilding the database from the start.

During TigerGraph Platform Installation, please specify ReplicationFactor during the installation for HA configuration. Default value for Replication Factor is 1, which means there is no HA setup for the cluster. If this value is set to a value higher than R (greater than 1), that means each partition should have R replicas.

If R is not a factor of the number of nodes in the cluster, then there might be some nodes unused