Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Learning VMware vRealize Automation

You're reading from   Learning VMware vRealize Automation Learn the fundamentals of vRealize Automation to accelerate the delivery of your IT services

Arrow left icon
Product type Paperback
Published in Feb 2016
Publisher Packt
ISBN-13 9781785885839
Length 230 pages
Edition 1st Edition
Arrow right icon
Author (1):
Arrow left icon
Sriram Rajendran Sriram Rajendran
Author Profile Icon Sriram Rajendran
Sriram Rajendran
Arrow right icon
View More author details
Toc

Table of Contents (10) Chapters Close

Preface 1. vRealize Automation and the Deconstruction of Components FREE CHAPTER 2. Distributed Installation Using Custom Certificates 3. Functional Validation – Phase 1 and Installing Secondary Nodes 4. Configuring a Guest OS for vRealize Automation vSphere Blueprints 5. Functional Validation – Phase 2 and Zero to VM Provisioning 6. Testing Failover Scenarios for vRealize Automation Components 7. vRealize Orchestrator in High Availability via the NSX Load Balancer 8. The Power of Advanced Service Designer (ASD) Index

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 page

  • The other vRealize Orchestrator nodes in the cluster determine that it is nonresponsive and take over the workflows

  • Once the server is ready to be brought online after fixing the issue, it's recommended to restart the impacted Orchestrator...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image