vRealize Orchestrator high availability mechanism
VMware vRealize Orchestrator nodes update their heartbeat in the database every 5 seconds. The default number of missed heartbeats that indicates a problem on a node is 3 heartbeats.
If a vRealize Orchestrator node has a problem and stops the heartbeat, vRealize Orchestrator is aware that its heartbeat has stopped. When the heartbeat entry in the database is not updated, other vRealize Orchestrator nodes in the cluster will know that the heartbeat of the node with a problem has stopped.
When the timeout is reached, the following happens:
- The vRealize Orchestrator node with the problem disappears from the Started Cluster Nodes section under the Server Availability option in the Orchestrator configuration ...
Get Learning VMware vRealize Automation now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
