background preloader

Clustering

Facebook Twitter

Load-balancing

Heartbeat. Clustering and High Availability : Failover Clustering with Hype. Hi cluster fans, The Cluster Program Management team recently returned from one of our biggest industry events and the second most popular question was “What is the best way to deploy Hyper-V with Failover Clustering?” (The most popular question being “What’s new in 2008 Failover Clustering” – see our recent post for that discussion: The answer really depends on your enterprise’s needs. You can host and fail over virtual machines (VMs) by making your physical machines highly available – this is known as ‘Host Clustering’ and is perhaps the most common and recommended deployment. This allows you to put each service or application in multiple individual VMs which are highly available. If a VM becomes unavailable, only that single service in that VM will fail over (assuming each VM has its own LUN).

By combining your guest and host clustering you can create high-availability in both your physical and virtual layers. Thanks, The UltraMonkey solution for LVS. Ultra Monkey is a project to create load balanced and highly available services on a local area network using Open Source components on the Linux operating system, including heartbeat and ldirectord from the Linux-HA project. Now we're going to using UltraMonkey to contruct a highly-available VS/NAT web cluster with two load balancers and three web servers. The topology is illustrated in the following figure. In the example, virtual IP address and gateway IP address are 10.23.8.80 and 172.18.1.254, which are floating between the two load balancers (LD1 and LD2), and the ip addresses of three real servers are 172.18.1.11, 172.18.1.12 and 172.18.1.13 respectively.

The configuration files of UltraMonkey are the same at LD1 and LD2. The configuration files for above examples are as follows: /etc/ha.d/ha.cf: logfacility local0 keepalive 2 deadtime 10 warntime 10 initdead 10 nice_failback on udpport 694 bcast eth1 node ld1 node ld2 /etc/ha.d/haresources: /etc/ha.d/ldirectord.cf: Digicube - Serveur dedie a 15 €/mois, 1Go ram, HD 80Go, CPU 1,6G.

How To Set Up A Load-Balanced MySQL Cluster | HowtoForge - Linux. Version 1.0 Author: Falko Timme This tutorial shows how to configure a MySQL 5 cluster with three nodes: two storage nodes and one management node. This cluster is load-balanced by a high-availability load balancer that in fact has two nodes that use the Ultra Monkey package which provides heartbeat (for checking if the other node is still alive) and ldirectord (to split up the requests to the nodes of the MySQL cluster).

In this document I use Debian Sarge for all nodes. Therefore the setup might differ a bit for other distributions. The MySQL version I use in this setup is 5.0.19. If you do not want to use MySQL 5, you can use MySQL 4.1 as well, although I haven't tested it. This howto is meant as a practical guide; it does not cover the theoretical backgrounds.

This document comes without warranty of any kind! 1 My Servers I use the following Debian servers that are all in the same network (192.168.0.x in this example): In addition to that we need a virtual IP address : 192.168.0.105. MLN - Manage Large Networks. Enomalism : Elastic Computing Platform - Virtual Server Manageme. SteelEye Technology – LifeKeeper, high availability clustering,