Activate High Availability Cluster

The High Availability (HA) Cluster feature in EasyEdge allows you to configure multiple EdgeNodes in a Primary/Replicas setup. This ensures that if the Primary gateway fails, one of the Replicas automatically takes over, maintaining data flow with minimal interruption.

This guide explains how to configure and activate an HA Cluster in EasyEdge Studio.

🎥 Video Tutorial: Watch the full step-by-step installation walkthrough below.

---

Step-by-Step Guide

1. Access EdgeNodes

From the System Overview, locate the EdgeNodes section. Confirm that you have at least two healthy EdgeNodes available.

2. Select the Primary Gateway

Click on the EdgeNode that holds the full project configuration. This EdgeNode will become the Primary in the cluster.

3. Open High Availability Settings

Inside the EdgeNode details page, go to the High Availability tab. Scroll down to the HA Cluster EdgeNodes section and click Bind EdgeNode.

4. Bind a Replica EdgeNode

In the overlay, select an eligible EdgeNode from the list.

• Only gateways that are healthy, with no project, and not already bound to a cluster will be available.

• Once selected, the Replica will be added to the cluster.

5. Deploy the Project

Deploy the project to the Primary gateway.

• The Replica does not need to be selected; it will automatically receive the same configuration as the Primary during deployment.

6. Verify Cluster Status

After deployment, return to the System Overview.

• The Primary EdgeNode will show as Healthy (Running).

• The Replica EdgeNode will show as Healthy (Standby).

7. Test Failover (Optional)

To simulate failover, stop the Primary gateway.

• The Replica will automatically change from Healthy (Standby) to Healthy (Running).

• Data will continue flowing to your applications with minimal disruption.

When the Primary gateway is restarted, it will rejoin the cluster as Healthy (Standby).

---

Key Notes

• A Primary EdgeNode can have unlimited Replicas.

• All EdgeNodes in the cluster must share the same architecture.

• Project deployments always start from the Primary; all Replicas will automatically mirror the configuration.