Cluster Config

MySQL Cluster Sandbox - pre-defined packages

MySQL Cluster Sandbox let's you get going within seconds. The packages contains a number of scripts to install, setup, and run MySQL CLuster and are intended for localhost installation only. They can be used for evaluation and development, as well as getting familiar with MySQL Cluster. Disk intensive, i.e write intensive apps, should use a real distributed setup. Otherwise there is a big chance that you will overload the disk subsystem. The data nodes will complain about "Redo logs overloaded" or something about "Redobuffer". If you want to have a real distributed setup, please use the configurator!

The packages comes with:

1 management server

2 data nodes

2 mysql servers

All processes are running on localhost! Please read the README to see the directory structure of the packages.

You can install the packages as any user! It will be self-contained in one single directory! You can also chose ports so that you can test with several versions, or also setup replication between two clusters on localhost!

Choose if you want to use the Pre-packaged configurations (fixed ports) or create a Custom configuration where you set the ports yourself.

Whatever you chose the scripts can automatically download and compile the latest source code release, or you can download the latest binary release from dev.mysql.cluster/downloads/cluster

Pre-packaged

You can choose from three types of Sandboxes (no replication, master cluster and slave cluster) and also thee different sizes:

Looking for 6.4? For now you have to use the Custom Sandbox.

Small - suitable for a computer with 1-2GB of RAM. 2GB is required if fully loaded up with data.

Medium - suitable for a computer with ~4GB of RAM. 4GB is required if fully loaded up with data.

Large - suitable for a computer with ~8GB of RAM.

The following ports are used in the packages (see below for details): 1186 and 1187 (management server), 3306, 3307, 3310, 3311 (mysql servers).

Small

package	ports used	download	extra info	cluster version
no replication	1186, 3306, 3307	mysqlcluster-63.tar.gz	DataMemory=256M	6.3
master cluster	1186, 3306, 3307	mysqlcluster-63-master.tar.gz	DataMemory=256M	6.3
slave cluster	1187, 3310, 3311	mysqlcluster-63-slave.tar.gz	DataMemory=256M	6.3

Medium

package	ports used	download	extra info	cluster version
no replication	1186, 3306, 3307	mysqlcluster-63.tar.gz	DataMemory=1024M	6.3
master cluster	1186, 3306, 3307	mysqlcluster-63-master.tar.gz	DataMemory=1024M	6.3
slave cluster	1187, 3310, 3311	mysqlcluster-63-slave.tar.gz	DataMemory=1024M	6.3

Large

package	ports used	download	extra info	cluster version
no replication	1186, 3306, 3307	mysqlcluster-63.tar.gz	DataMemory=2560M	6.3
master cluster	1186, 3306, 3307	mysqlcluster-63-master.tar.gz	DataMemory=2560M	6.3
slave cluster	1187, 3310, 3311	mysqlcluster-63-slave.tar.gz	DataMemory=2560M	6.3

Installation - Pre-packaged and Custom

Download the package and also the tar.gz distro from dev.mysql.cluster/downloads/cluster If you want to use a

tar xvfz mysqlcluster-63-<type>.tar.gz

cd mysqlcluster-63-<type>

Continue from either "To build from source" or "Using a tar.gz distro"

To build from source

In order to build from source you need to have the following software installed:

wget

GNU gcc/g++/make

Then run the following four scripts

download-and-compile.sh - gets the latest officially released cluster source, configure, and build. The resulting build is in the build/ directory

dist-src-build.sh - Distribute the binary located in build/mysql... to the hosts in the cluster

bootstrap.sh - sets up directory structures and installs the mysql servers configured with a hostname. The script will delete any old information (if a previous mysqld data directory exists on the same location) located on a host. Configuration files (my.cnf and config.ini) will be installed in /etc/mysql/

start-cluster-initial.sh - starts the management server(s), the data nodes and the mysql server(s) configured with a hostname

Using a tar.gz distro

Download the binary tar package (RPMs etc does not work with this) from mysql

dist-tgz.sh - Distribute the binary and upacks them on to the hosts in the cluster

start-cluster-initial.sh - starts the management server(s), the data nodes and the mysql server(s) configured with a hostname

After this you can the use the other scripts:

show.sh - shows the nodes connected to the cluster

status.sh - prints the status of the data nodes in the cluster

start-backup.sh "directory" - starts a backup and copies the backup files from the data nodes and puts them in the "directory" (which must exist) and removes the local backup on the data nodes.

There are also scripts to stop the cluster, start and stop individual nodes. E.g:

start-ndbd-... - start a ndbd node on a particular host (there are also scripts to start with --initial)

stop-ndbd-... - stops a ndbd node on a particular host

start-mysqld-... - starts a mysqld on a particular host

stop-mysqld-... - stops a mysqld node on a particular host

stop-cluster.sh - stops management servers, data nodes and also the mysql servers (if present in the script variable 'mysql_hostnames')

rolling-restart.sh... - updates the cluster with a new version or with changed configuration parameters (such as more mysql servers or more data memory (you must recalculate the size of the redo log then). Please note that some parameter changes requires an initial rolling restart (especially file system related parameters. See the reference manual). Moreover, you should update the config/config.ini since that is the one being distributed to the management servers. Please not that you can't change NoOfReplicas or add more data nodes using rolling restart (yet). If you try you will have a cluster failure to sort out. You can also upgrade to a new version (never downgrade) using dist.sh (which will download a new version if it exists) and then use rolling-restart.sh to upgrade to that version.

rolling-restart-initial.sh... - For parameters requiring an initial rolling restart..(NoOfFragmentLogfiles, FragmentLogFileSize, DataDir...)

Support

Let us know if you have issues with the scripts by mailing support at severalnines dot com