MySQL Cluster

A rolling restart is required when you need to restart all of the nodes in a cluster for some change to take effect. Rather than bringing down the entire cluster, you can restart each single node one by one, in order to allow the cluster to continue serving requests during the changes. Most operations can be done using this technique, such as changing config.ini settings (ie. DataMemory, MaxNoOfConcurrentTransactions, etc.). However, there is a main instance when you can not use this process … [Read more...] about How to Perform a Rolling Restart of MySQL NDB Cluster

There are three types of nodes that you might want to add to an existing MySQL Cluster: mysqld (API) nodes, management server nodes, and data nodes. Adding a new mysqld (API) node In order to add a new mysqld node, you simply need to add the new [mysqld] section to the config.ini and then perform a rolling upgrade. After you have done this, then you can start up the new mysqld node and it will have all of the cluster data available. To do this, following you would follow these steps: Edit … [Read more...] about How to Add New Nodes To an Existing MySQL Cluster Setup

The ability to add MySQL Cluster data nodes while the cluster is still up and running is known as performing an "online" addition of nodes. This became available in MySQL Cluster starting with the 6.4.0 release version. Performing an online addition to the cluster allows for increased availability since there is no downtime and also allows a more flexible management of the cluster resources. Certain changes of the Cluster configuration will require a complete restart of the Cluster and even a … [Read more...] about How to Add Data Nodes to MySQL Cluster without Restarting the Cluster (version 6.4 and later)

It is possible but not advisable. One of the main reasons to run a cluster is to provide redundancy: in order to enjoy the full benefits of this redundancy, each node should reside on a separate machine. If you place multiple nodes on a single machine and that machine fails, you lose all of those nodes. Given that MySQL Cluster can be run on commodity hardware loaded with a low-cost (or even no-cost) operating system, it is well worth the expense of an extra machine or two in order to … [Read more...] about Can MySQL Cluster Run Multiple Nodes On a Single Server

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 with a minimum of specific requirements for hardware or software. MySQL Cluster is designed not to have any single point of failure. It integrates the standard MySQL server with an in-memory clustered storage engine called NDB. MySQL Cluster refers to the combination of MySQL and the NDB storage … [Read more...] about How to Install MySQL Cluster on a single server for testing purposes

Overview of the Cluster Logs MySQL Cluster can be complicated in nature and this requires a more sophisticated method of logging to manage all the information. The logging can be performed at a global level indicating the overall health of the cluster and how the nodes are interacting. There is also a local logging level which gives the status of the specific node and any internal errors that may, or may not, be affecting other nodes. The global logging of the cluster is done via log events … [Read more...] about Beginners Guide to Management of MySQL Cluster Log Files

Important: The native NDB Cluster backup only includes information for tables using the NDBCluster storage engine. If you need to restore views, stored procedures, stored functions, events, and tables using other storage engines, you must restore them from a mysqldump, mysqlpump, or other backup. The backup created a set of files for each data node that was online at the time of the backup. The files are located below the directory specified by the BackupDataDir option in the directory … [Read more...] about How To Restore an NDBCluster Backup Using ndb_restore

MySQL Cluster provides what is known as geographical replication, a situation in which a cluster is running in two data centers: one as Master, the other as Slave. This allows you to backup up both using MySQL Cluster's online backup functionality. Usually, when the Slave is out of sync, you simply reset it as a new slave, using a fresh snapshot of the Master. However, as an alternative, you can use the backup of the Slave instead. This could prove to be a faster method of reinstalling the slave … [Read more...] about How to Restore a Cluster Slave Using its Own Backups

If you're using MySQL Cluster and want to restore data from a specific point-in-time after the last backup of a database, you can do so by replaying binary log entries from the last backup up until a specified point in time. The data restoration covered in this article only involves MySQL Cluster. It does not cover other storage engines. Note: All NDB tables must have a primary key defined or this procedure will not work as expected. Four steps are involved. Make sure that these steps are … [Read more...] about MySQL Cluster Point-In-Time Recovery (PITR)

One of the key aspects of a highly-available system is that routine maintenance can be carried out without any service interruption to users. MySQL Cluster achieves this through its shared-nothing architecture, and in this recipe, we will show how to restart the three types of nodes online (without taking the cluster down as a whole). The setup For this post, we will be using the following cluster setup: Four storage nodes One management node Two SQL nodes The output of the SHOW … [Read more...] about How to Restart a MySQL Cluster without downtime