# 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**.

{% hint style="info" %}
🎥 **Video Tutorial:**\
\&#xNAN;*Watch the full step-by-step installation walkthrough below.*
{% endhint %}

{% embed url="<https://www.youtube.com/watch?v=2-ntHaPxXUE>" %}

***

## 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.

<figure><img src="/files/Xfo1a62HabF2UfxTFYwo" alt=""><figcaption></figcaption></figure>

### 2. Select the Primary Gateway

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

<figure><img src="/files/qHuHSlUtwzSiiQ5CvbjQ" alt=""><figcaption></figcaption></figure>

### 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**.

<figure><img src="/files/zeR0TL3PoFOOU4dhLTeM" alt=""><figcaption></figcaption></figure>

### 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.

<figure><img src="/files/FAQopdLjND5He0fSvkmd" alt=""><figcaption></figcaption></figure>

### 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.

<figure><img src="/files/kUfi0hz41OvfBrRR4j5B" alt=""><figcaption></figcaption></figure>

### 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)**.

<figure><img src="/files/evAFlxHEjAidhtHrdIH9" alt=""><figcaption></figcaption></figure>

### 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)**.

<figure><img src="/files/HbnStjAimFH9SP5aPDrZ" alt=""><figcaption></figcaption></figure>

***

## 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.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://easyedge.gitbook.io/easyedge/add-and-configure-edgenodes/configure-edgenodes/activate-high-availability-cluster.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.