标签归档:MySQL Cluster

MySQL Cluster fault tolerance – impact of deployment decisions

MySQL Cluster fault tolerance – impact of deployment decisions

Typical management configuration

Fig 1. Typical management configuration

MySQL Cluster is designed to be a High Availability, Fault Tolerant database where no single failure results in any loss of service.

This is however dependent on how the user chooses to architect the configuration – in terms of which nodes are placed on which physical hosts, and which physical resources each physical host is dependent on (for example if the two blades containing the data nodes making up a particular node group are cooled by the same fan then the failure of that fan could result in the loss of the whole database).

Of course, there’s always the possibility of an entire data center being lost due to earthquake, sabotage etc. and so for a fully available system, you should consider using asynchronous replication to a geographically remote Cluster.

Fig 1. illustrates a typical small configuration with one or more data nodes from different node groups being stored on two different physical hosts and a management node on an independent machines (probably co-located with other applications as its resource requirements are minimal. If any single node (process) or physical host is lost then service can continue.

继续阅读

How To Set Up A Load-Balanced MySQL Cluster

Version 1.0
Author: Falko Timme <ft [at] falkotimme [dot] com>
Last edited 03/27/2006

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. They are treated in a lot of other documents in the web.

This document comes without warranty of any kind! I want to say that this is not the only way of setting up such a system. There are many ways of achieving this goal but this is the way I take. I do not issue any guarantee that this will work for you! 继续阅读

MySQL Cluster: Two webserver setup

MySQL Cluster: Two webserver setup

HOWTO set up a MySQL Cluster for two servers (three servers required for true redundancy)
Introduction
This HOWTO was designed for a classic setup of two servers behind a loadbalancer. The aim is to have true redundancy – either server can be unplugged and yet the site will remain up.
继续阅读

How To Set Up A Load-Balanced MySQL Cluster

http://www.howtoforge.com/loadbalanced_mysql_cluster_debian
Version 1.0
Author: Falko Timme
Last edited 03/27/2006

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). 继续阅读

MySQL Cluster in 5 Minutes

This article shows the simplest setup of a MySQL cluster. No whistles and bells, just to get started.

You have heard about MySQL Cluster, but you were always afraid to get into it because „Cluster“ seems to be a magic and complicated topic? Then this article is for you. In a couple of minutes, you can run your own Cluster.

Sometimes, I need to demonstrate how MySQL cluster works. I usually set up a single machine cluster which of course won‘t make sense in production scenarios, but for an introduction into MySQL cluster it‘s fine. And it‘s very easy to deploy the system on multiple machines later. 继续阅读