UiPath Orchestrator

The UiPath Orchestrator Guide

Hardware and Software Requirements

Hardware Requirements

The hardware requirements for your High Availability Add-on (HAA) are different between development and production environments.

Development Environments

ItemMinimum RequirementsRecommended
HAA Nodes13+
Storage10 GB20 GB

While one node is sufficient for a development environment, three or an odd number of nodes are recommended in order to utilize the clustering features likely needed for your production environment.

Production Environments

ItemMinimum RequirementsRecommended
HAA Nodes33+
Cores per Node48+
(15 GB for DR deployments)
30+ GB
Storage75 GB150+ GB
Network1 G10+ G

Note: Always maintain an odd number of nodes. This is required to obtain a quorum needed in failure and failover scenarios.


1968Default port used for internal proxy traffic.
Default port ranges used for internal cluster traffic.
8001Used for traffic from the application to the Discovery Service, if applicable.
8443Used for HTTPS access to the management UI.
8444 , 9080Default ports used for internal nginx < - > cnm_http/cm traffic.
9081Default port used for internal CRDB (Conflict-free Replicated Database) traffic.
8070-8071Used for metrics exported and managed by nginx.
9443Recommended port for REST API traffic.
10000-19999Port range for database traffic. By default, HAA uses port 10000.
20000-29999Port range used for internal database shards traffic.
53, 5353Used for internal DNS/mDNS traffic.

Software Requirements



HAA only supports 64-bit operating systems and must be installed on a clean host with no other applications and synchronized with the same NTP server.

PlatformSupported Versions
RHEL/CentOS 7 7.0 - 7.6 (Requires at least Minimal Install configuration)

General Cluster Requirements

The HAA cluster needs three servers for a healthy operation.
Under normal circumstances, the HAA cluster servers have the following roles:

  • one principal server – it holds a data shard, and it accepts read and write database operations from the outside world;
  • one secondary server – it holds a copy of the data shard;
  • one secondary serve – it holds no data, it exists for quorum purposes only.

The HAA cluster supports a single server failure only.

  • If one of the servers goes down, no matter which one, the HAA cluster continues working, and a warning is shown in the Web management interface. You can find more information by running the rlcheck command, usually found in /opt/redislabs/bin. You can also append --continue-on-error to the rlcheck command.
  • If two servers fail, the HAA cluster fails as well, even if the principal server is still online.

Building an HAA cluster with more than three servers is possible but offers no real benefit.
There is no increase in the number of servers that can fail. In the case of a five-node HAA cluster, if the principal node and the secondary node keeping the data shard copy both fail, the entire cluster fails as well, and there is no data shard reallocation to other nodes.

Updated 6 months ago

Hardware and Software Requirements

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.