MySQL Cluster Manager 8.0 User Manual  /  What Is New in MySQL Cluster Manager 8.0

Chapter 2 What Is New in MySQL Cluster Manager 8.0

Here is a summary of the major changes for MySQL Cluster Manager going from series 1.4 to series 8.0:

  • MySQL Cluster Manager 8.0 supports MySQL NDB Cluster 7.5, 7.6, and 8.0. It does not support MySQL NDB Cluster 7.3 and 7.4.

  • MySQL Cluster Manager 8.0 uses a new format for its configuration file, which is the same format used by MySQL Router. See Section 3.4, “MySQL Cluster Manager Configuration File” for details.

    Note

    MySQL Cluster Manager expects that configuration files of the new format use .conf as its filename extension. If the .ini extension is used, the configuration file is still accepted; but if the file also includes option names containing hyphens (instead of underscores), the following error is thrown:

    Old config file name and contents detected. Please ensure an updated config
    file is used.
    Error: Configuration error: Invalid option name option-name
  • A number of MySQL Cluster Manager Agent (mcmd) options have changed. The following table list the changes:

    Table 2.1 Changes of mcmd Options from Series 1.4 to 8.0

    mcmd 1.4 mcmd 8.0 Comments
    --help-all - Not available in 8.0
    --help-manager - Not available in 8.0
    --defaults-file=file -c <file> / --config=<file>

    also:

    -a <file> / --extra-config=file

    Use new options for 8.0
    --verbose-shutdown - Not available in 8.0
    --daemon - Not available in 8.0
    --agent-uuid - Not available in 8.0
    --basedir=path - Not available in 8.0. Relative paths for mcmd options are always resolved relative to the MySQL Cluster Manager installation directory.
    --plugin-dir=path - Not available in 8.0
    --plugins=name - Not available in 8.0
    --log-level=string level Use new option in 8.0. Must be set in the [logger] section of the configuration file for 8.0
    --log-file=file filename, logging_folder Use new options for 8.0. filename must be set in the [logger] section and logging_folder in the [DEFAULT] section of the configuration file for 8.0
    --log-use-syslog - Not available in 8.0
    --log-backtrace-on-crash - Not available in 8.0
    --keepalive - Not available in 8.0
    --max-open-files - Not available in 8.0
    --event-threads - Not available in 8.0
    --bootstrap -B / --bootstrap Added short form for 8.0
    --initial -i / --initial Added short form for 8.0
    --manager-directory=directory -d <directory>, --data-folder <directory> Use new option for 8.0. When set in the configuration file, the option should be put inside the [DEFAULT] section.
    --manager-password=password mcmd_password Not available in 8.0 due to security reasons. Must be set in configuration file in the [mcmd] section.
    --manager-port=client_port --bind-port portnumber Use new option for 8.0. When set in the configuration file, the option should be placed in the [mcmd] section.
    --manager-username=username --mcmd-user=<username> Use new option for 8.0. When set in the configuration file, the option should be put inside the [mcmd] section.

  • A number of MySQL Cluster Manager Client (mcm) options have changed. The following table list the changes:

    Table 2.2 Changes of mcm Options from Series 1.4 to 8.0

    mcmd 1.4 mcmd 8.0 Comments
    -W - Not available in 8.0
    --address, -a

    -h host_name / --host=host_name and -P port_number / --port=port_number

    Use different options for 8.0
    --mysql-help - Not available in 8.0

  • Files collected by the collect logs command from cluster nodes are now organized under a new folder structure; see the description for the command for details.

  • MySQL Cluster Manager 8.0 has a new init script for running mcmd as a daemon on Linux platforms. See MySQL Cluster Manager init script. You should be aware that the changes mentioned previously in the configuration file format and the agent options also apply, when you use the init script.

  • Agent log levels have changed; see Table 4.2, “MySQL Cluster Manager Agent Log Levels”, for more information.

  • MySQL Cluster Manager 8.0.31 and later supports NDB Cluster Transparent Data Encryption (TDE), which encrypts all user data stored in NDB tables. For information about enabling TDE support in MySQL Cluster Manager, see Setting Up Encryption. For more information about how NDB implements TDE, see File System Encryption for NDB Cluster.

  • For other changes, see MySQL Cluster Manager 8.0 Release Notes.