> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xsoar-8-on-prem/8.6/onboard-cortex-xsoar/cortex-xsoar-installation/high-availability-for-cortex-xsoar.md).

# High Availability for Cortex XSOAR

For a single data center, when you deploy a cluster of three nodes, you can implement built-in High Availability (HA). Cortex XSOAR on-prem currently supports an HA solution for a use case of node failure, in which the system experiences downtime and then restores automatically.

A cluster of three nodes enables distributing the workload and replicating data across the nodes to ensure continuous operation. If one node fails, the remaining nodes take over the tasks and data handling, minimizing downtime and maintaining service availability. This setup allows for redundancy and enhances the overall resilience of the system.

{% hint style="info" %}

### Note

Kubernetes requires a majority of control plane nodes to be online for it to function, so a three-node cluster requires two to be online. If two nodes fail but are fixed and go back online, the cluster will recover. However, if two nodes fail and are not able to go back online, open a support session for assistance.
{% endhint %}

Built-in High Availability works as follows:

* Tasks and data are distributed across the nodes to balance the load.
* Data is replicated across nodes, ensuring no single point of failure.
* If a node goes down, workloads on the failed node are automatically distributed to the other nodes.

  <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><h3>Note</h3><p>There may bea several minutes of downtime until the other nodes take over.</p></div>
* Once the failed node is restored, it automatically reintegrates into the cluster and the workloads are automatically rescheduled.

### Monitor and manage nodes

Once you set up your cluster and install Cortex XSOAR, you can monitor node status and recover from node failure as needed.

1. In Cortex XSOAR, monitor the node health in the **System Diagnostics** page. For more information, see [View system status in the System Diagnostics page](/cortex-xsoar-8-on-prem/8.6/troubleshoot-and-reference/troubleshoot/view-system-status-in-the-system-diagnostics-page.md).
2. If there is a node failure, manage the nodes from the textual UI.

   For example, if a node fails, remove it and then add a new node to replace it. For more information, see [Manage nodes in a cluster](/cortex-xsoar-8-on-prem/8.6/onboard-cortex-xsoar/cortex-xsoar-installation/post-installation/manage-nodes-in-a-cluster.md).

   You need to set the host again and reestablish trust between all the nodes if you want to replace a node in the cluster after completing installation.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/cortex-xsoar-8-on-prem/8.6/onboard-cortex-xsoar/cortex-xsoar-installation/high-availability-for-cortex-xsoar.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.