Hi,

I have tried to basics mysql clustring on MySQL5.1 have used the same how to posted by me at:

http://forums.linuxwebadmin.info/index.php...topic,90.0.html



MySQL Clustering How-to - Easy step by step guide

MySQL Cluster is a technology that enables clustering of in-memory databases in a shared-nothing system. The shared-nothing architecture allows the system to work with very inexpensive hardware, and without any specific requirements on hardware or software. It also does not have any single point of failure because each component has its own memory and disk.

A MySQL Cluster consists of a set of computers, each running a one or more processes which may include a MySQL server, a data node, a management server, and (possibly) a specialized data access programs. All these programs work together to form a MySQL Cluster.

There are three types of cluster nodes, and in a minimal MySQL Cluster configuration, there will be at least three nodes, one of each of these types:

Management node (MGM nod.): The role of this type of node is to manage the other nodes within the MySQL Cluster.

Data node: This type of node stores cluster data. There are as many data nodes as there are replicas, times the number of fragments.

SQL node: This is a node that accesses the cluster data. An SQL node is typically started with the command mysqld --ndbcluster or by using mysqld with the ndbcluster option added to my.cnf.

Assumptions:
1. The cluster setup has four nodes, each on a separate host, and each with a fixed network address on a typical Ethernet as shown here:

Consider that each host is with enough ram and good hardware configuration.

Packages Specification:

MySQL-server-VERSION.i386.rpm
The MySQL server. You need this unless you only want to connect to a MySQL server running on another machine.

MySQL-client-VERSION.i386.rpm
The standard MySQL client programs. You probably always want to install this package

MySQL-bench-VERSION.i386.rpm
Tests and benchmarks. Requires Perl and the DBI and DBD::mysql modules.

MySQL-devel-VERSION.i386.rpm
The libraries and include files that are needed if you want to compile other MySQL clients, such as the Perl modules.

MySQL-shared-VERSION.i386.rpm
This package contains the shared libraries (libmysqlclient.so*) that certain languages and applications need to dynamically load and use MySQL. It contains single-threaded and thread-safe libraries. If you install this package, do not install the MySQL-shared-compat package.

MySQL-ndb-storage-VERSION.i386.rpm
NDB Cluster - Storage engine (contains the NDB Data Node program)

MySQL-ndb-management-VERSION.i386.rpm
NDB Cluster - Storage engine management (contains the NDB Management Server)

MySQL-ndb-tools-VERSION.i386.rpm
NDB Cluster - Storage engine basic tools

MySQL-ndb-extra-VERSION.i386.rpm
NDB Cluster - Storage engine extra tools

Cont.....

Package requirement:

192.168.2.159 - MySQL server (SQL) node
MySQL-server-5.1.11-0.glibc23
MySQL-shared-5.1.11-0.glibc23
MySQL-client-5.1.11-0.glibc23

192.168.2.160 - Management (MGM) node
MySQL-ndb-tools-5.1.11-0.glibc23
MySQL-ndb-management-5.1.11-0.glibc23

192.168.2.161 - Data (NDBD) node "A"
MySQL-ndb-tools-5.1.11-0.glibc23
MySQL-client-5.1.11-0.glibc23
MySQL-ndb-storage-5.1.11-0.glibc23
MySQL-server-5.1.11-0.glibc23 ( Optional )

192.168.2.162 - Data (NDBD) node "B"
MySQL-ndb-tools-5.1.11-0.glibc23
MySQL-client-5.1.11-0.glibc23
MySQL-ndb-storage-5.1.11-0.glibc23
MySQL-server-5.1.11-0.glibc23 ( Optional )

Step by Step configuration:

Each data node or SQL node requires a my.cnf file that provides two pieces of information:
- A connect string to find the MGM node
- A line which says the MySQL server on this host to run in NDB mode.

The my.cnf file for data node (ndb)

For each data node and SQL node in our example setup(i.e. Data (NDBD) node "A" 192.168.2.161 & Data (NDBD) node"B" 192.168.2.162) my.cnf should look like this:




Cont......

Now, you need to start the actual cluster:

The Management Node configuration:

You need to create a directory in MGM node to in which the configuration file can be found and then to create file it self.





Cont....

Then, you need to start a cluster which as been configured; each cluster node process must be started separately.

It is recommended that the management node be started first, followed by the storage nodes, and then finally by any SQL nodes:

In MGM node ( 192.168.2.160) pass the following command:



You must need to tell mgmd to find the configuration file.

Now, start the ndbd process in each data node A and B ( 192.168.2.161 & 192.168.2.162)



Then, start mysql server process on the SQL node (192.168.2.159)



Verify that SQL node is started with support of ndb cluster:



Cont....

If all has been setup correctly, the cluster should be operational.

Type the below mentioned command from Managment Node:



Here, you will find three API node as we have also configurd it as a API in config.ini.

You can obtain some information from a MySQL server running as a Cluster SQL node using SHOW STATUS in the mysql client, as shown here:



Cont...

How to shutdown and restart the cluster:

In MGM node use the below mentioned command:



The above command causes the ndb_mgm, ndb_mgmd, and any ndbd processes to terminate gracefully.

To restart the cluster:

From MGM node (192.168.2.160)



From Data Node (192.168.2.161 & 192.168.2.162)



From SQL node:



###End###

I have tried to set it up with your guide on linux red hat ES4
but fail

Below is detail:

management node on 192.168.0.28
data node on : 192.168.0.94, 192.168.0.95
sql node on : 192.168.0.94, 192.168.0.95

package
192.168.0.28
MySQL-Cluster-gpl-management-6.2.15-0.rhel4
MySQL-Cluster-gpl-tools-6.2.15-0.rhel4
MySQL-Cluster-gpl-storage-6.2.15-0.rhel4

192.168.0.94/95
MySQL-Cluster-gpl-client-6.2.15-0.rhel4
MySQL-Cluster-gpl-tools-6.2.15-0.rhel4
MySQL-Cluster-gpl-storage-6.2.15-0.rhel4
MySQL-Cluster-gpl-server-6.2.15-0.rhel4



config.ini
=======================================
# Options affecting ndbd processes on all data nodes:
[NDBD DEFAULT]
NoOfReplicas=2 # Number of replicas

[mysqld default]


# TCP/IP options:
[TCP DEFAULT]

# Management process options:
[NDB_MGMD]
hostname=192.168.0.28 # Hostname or IP address of MGM node
datadir=/var/lib/mysql-cluster # Directory for MGM node logfiles

# Options for data node "A":
[NDBD]
hostname=192.168.0.94 # Hostname or IP address
DataDir=/var/lib/mysql-cluster # Directory for this data node's datafiles
BackupDataDir=/var/lib/mysql-cluster/backup
#DataMemory=256M # Set this as per your server h/w
#TimeBetweenWatchDogCheck=5000
#TimeBetweenWatchDogCheckInitial=5000

# Options for data node "B":
[NDBD]
hostname=192.168.0.95 # Hostname or IP address
DataDir= /var/lib/mysql-cluster # Directory for this data node's datafiles
BackupDataDir=/var/lib/mysql-cluster/backup
#DataMemory = 256M # Set this as per your server h/w

# SQL node options:
[MYSQLD]
hostname=192.168.0.94 # Hostname or IP address
# (additional mysqld connections can be
# specified for this node for various
# purposes such as running ndb_restore)
[MYSQLD]
hostname=192.168.0.95 # Hostname or IP address

===========================================================


quote from my.cnf in 192.168.0.94
===========================
# Here follows entries for some specific programs
[mysqld]
ndbcluster # run NDB engine
ndb-connectstring=192.168.0.28 # location of MGM node

# Options for ndbd process:
[MYSQL_CLUSTER]
ndb-connectstring=192.168.0.28 # location of MGM node
===========================

I start the management node successful but when i start the data node
The following error found in the data node log


Time: Monday 14 July 2008 - 17:18:40
Status: Permanent error, external action needed
Message: Invalid configuration received from Management Server (Configuration error)
Error: 2350
Error data: Invalid configuration fetched
Error object: TimeBetweenWatchDogCheckInitial missing
Program: ndbd
Pid: 2504
Trace: /var/lib/mysql-cluster/ndb_2_trace.log.11
Version: mysql-5.1.23 ndb-6.2.15
***EOM***

Then I try to add another data node on 28(just for testing)
and the data node on 28 can start successfully

quote from my.cnf on 192.168.0.28
========================================
[MYSQLD]
ndbcluster # run NDB engine
ndb-connectstring=192.168.0.28 # location of MGM node

# Options for ndbd process:
[MYSQL_CLUSTER]
ndb-connectstring=192.168.0.28 # location of MGM node
# The MySQL server
========================================

My question is what cause the Error object: TimeBetweenWatchDogCheckInitial missing problem and how to fix it?

Terry, Manuel was last seen March 1st 2008, so I would try Private Messaging him with a link to your post asking for help. Otherwise, I don't think he checks the board regularly.

Thank you!