Prepare Storage for MySQL Cluster

For each of the node types being deployed the following storage should be provisioned from FlashArray.

Node Type	Storage Requirement	Volumes
Management Node	The management node will store event logs in the form of Cluster Logs and Node Logs. Ensure that the volume size is sufficient to store events as long as they need to be retained. It is possible to set a specific LogDestination but it is recommended that the logs are sent to the same destination as the datadir.	Per Management Node: 1 x min 128Gb volume.
Data Node	Data nodes store persisted database information. Each Data node needs to have (at minimum) a single volume with sufficient space for checkpoint data and redo logs. It is recommended to have a separate volume/location for backups.	Per Data Node: 1 x data storage volume (1.5x the amount of database data to be stored). 1 x backup volume (Number of retained backups x database data size) Note: The backup volume can be an NFS volume exported from FlashArray or FlashBlade.
SQL Node	SQL Nodes only require enough storage capacity for executables and local log files. Note: An SQL Node can store InnoDB data locally but this guide assumes only NDB clustering is required.	Per SQL Node: 1 x min 50Gb volume.

Node Type

Storage Requirement

Volumes

Management Node

The management node will store event logs in the form of Cluster Logs and Node Logs. Ensure that the volume size is sufficient to store events as long as they need to be retained.

It is possible to set a specific LogDestination but it is recommended that the logs are sent to the same destination as the datadir.

Per Management Node:

1 x min 128Gb volume.

Data Node

Data nodes store persisted database information. Each Data node needs to have (at minimum) a single volume with sufficient space for checkpoint data and redo logs.

It is recommended to have a separate volume/location for backups.

Per Data Node:

1 x data storage volume (1.5x the amount of database data to be stored).

1 x backup volume (Number of retained backups x database data size)

Note:

The backup volume can be an NFS volume exported from FlashArray or FlashBlade.

SQL Node

SQL Nodes only require enough storage capacity for executables and local log files.

Note:

An SQL Node can store InnoDB data locally but this guide assumes only NDB clustering is required.

Per SQL Node:

1 x min 50Gb volume.

Note:

As a MySQL cluster operates a Shared-Nothing architecture, the volumes only need to be connected to the respective node types.

Volumes are not shared between nodes thus each node type needs to have its own volume(s).

Once each of the nodes has the relevant storage connected to them, ensure each contains a file system and is mounted at the required locations.

Linux Example file system locations

Note:

XFS and EXT4 are both acceptable file systems for FlashArray volumes holding NDB data.

Management Node: /var/lib/mysql-cluster (DataDir)
Data Node: /usr/local/mysql/data (DataDir)
Data Node: /usr/local/mysql/backup(BackupDataDir)
SQL Node: /var/lib/mysql (dataDir)

Microsoft Windows Example File System Locations

Note:

The NTFS filesystem is recommended for FlashArray volumes holding NDB data on Microsoft WIndows.

Management Node: C:\Users\user1\my_cluster\ndb_data (DataDir)
Data Node: c:\Users\user1\my_cluster\ndb_data (DataDir)
Data Node: c:\Users\user1\my_cluster\ndb_backup (BackupDataDir)
SQL Node: c:\\Users\\user1\\my_cluster\\mysqld_data (dataDir)