![]() Thus, subsequent network traffic to the Floating IP will be directed to your secondary server, which will act as the active server until the primary server becomes available again (at which point, the primary server will reassign the Floating IP to itself). In the event that the Heartbeat service detects that the primary server is unavailable, the secondary server will automatically run a script to reassign the Floating IP to itself via the DigitalOcean API. This will be accomplished by pointing a Floating IP, which is how your users will access your services or website, to point to the primary - or active - server unless a failure is detected. When completed, the HA setup will consist of two Ubuntu 16.04 servers in an active/passive configuration. If you are looking to create a more robust HA setup, look into using Corosync and Pacemaker or Keepalived. Heartbeat is typically used in conjunction with a cluster resource manager (CRM), such as Pacemaker, to achieve a complete HA setup. In this tutorial, we will demonstrate how to create a 2-node HA server setup by simply using Heartbeat and a DigitalOcean Floating IP. These capabilities are a critical component in a high availability (HA) server infrastructure. Heartbeat is an open-source program that provides cluster infrastructure capabilities - cluster membership and messaging - to client servers. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |