- Primeros pasos
- Requisitos
- Mejores prácticas
- Instalación
- Actualizando
- Servidor de identidad
- High Availability Add-on
If your deployment has grown and you need to increase capacity, expanding your Orchestrator to a multi-node installation is the next logical step. It offers both better performance and failure resistance as multiple Orchestrator nodes are available - when one fails, the other(s) can pick up the load. Horizontal scalability is also available, as it is possible to add additional nodes as your Robot needs grow further. This deployment model should not, however, be confused with High Availability, as the lone HAA node remains as a potential single point of failure.
Remember to take into consideration the Orchestrator hardware requirements corresponding to the scale of your deployment.
Please note that this model is more resource intensive than a single node installation, requiring additional components such as the High Availability add-on for Orchestrator (or other tested solution) and a network load balancer.
El siguiente diagrama representa una implementación multinodo sencilla de dos o tres nodos de Orchestrator sincronizados mediante un solo nodo HAA:
UiPath admite las implementaciones de Orchestrator multinodo solo si se usa la adición de alta disponibilidad de UiPath.
Estas implementaciones utilizan el RESP (Protocopo de serialización REdis) para la comunicación y, por tanto, se pueden configurar utilizando cualquier solución que implementa este protocolo. Las soluciones potenciales probadas (pero no compatibles) por UiPath son:
- Redis de MSOpenTech en Windows v3.0.504
- Servidor Redis v3.2.8 y v5.0.4
- Redis Enterprise v5.4.0-19