home      tools      best practices      web resources      blog
Cluster Config

MySQL Cluster Sandbox - Custom

Pre-packaged Custom Installation Support

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

    Custom

    Cluster version: MySQL Cluster 6.3 is recommended for general purpose.
    MySQL Cluster 7.0 is beta but has lot of new cool features (e.g multithreading, online add node).
    Why not 6.2? Well, 6.3 is much better! The main differences between 6.2 and 6.3 is that 6.3 has better support for Realtime and the geo-redundancy supports Conflict Detection and Resolution, as well as memory deallocation. Read here for more information about the differences.

    There are prebuilt binaries for MySQL Cluster 6.3, but the source releases are released more frequently.
    Configuration size
  • Tiny - DataMemory=80MB. Suitable for a computer with ~512MB of RAM. E.g a small VMWARE instance on a laptop. No serious work can be done on this. 1GB of RAM is required to fill it up and void swapping.
  • Small - DataMemory=256MB. Suitable for a computer with 1-2GB of RAM. 2GB is required if fully loaded up with data.
  • Medium - DataMemory=1024MB. Suitable for a computer with ~4GB of RAM. 4GB is required if fully loaded up with data.
  • Large - DataMemory=2560MB. Suitable for a computer with ~8GB of RAM.

    • Please note that often it is the disk subsystem that will be the bottleneck, especially when running on localhost. This means that a "large" requires a good disk subsystem even on localhost.

    You can check this file about approx. memory usage as reported from top (opens a new tab/window)\n";
    Port for management server:
    		Which port the management server should listen on. Make sure you use unique ports if you will deploy several clusters on the same host!
    Port for mysql server 1:
    		Which port the first mysql server will listen on. Make sure you use unique ports if you will deploy several clusters on the same host!
    Port for mysql server 2:
    		Which port the second mysql server will listen on. Make sure you use unique ports if you will deploy several clusters on the same host!
    Replication role:
  • None - the cluster will not be used in replication
  • Master - the cluster will act as the replication master (one or more mysqlds will produce binary logs)
  • Slave - the cluster will act as a standby cluster
    		•
    Number of cores: Only applicable for MySQL Cluster 7.0!
    Specify how many cores to dedicate to the data nodes.
    no MT - use this if you want to use single threaded data nodes (good for laptops).
    Email: