Documentation Home
MySQL NDB Cluster 6.1 - 7.1 Release Notes
Download these Release Notes
PDF (US Ltr) - 3.0Mb
PDF (A4) - 3.0Mb

MySQL NDB Cluster 6.1 - 7.1 Release Notes  /  Changes in MySQL Cluster NDB 7.1  /  Changes in MySQL Cluster NDB 7.1.0 (5.1.39-ndb-7.1.0) (Not released, alpha)

Changes in MySQL Cluster NDB 7.1.0 (5.1.39-ndb-7.1.0) (Not released, alpha)

This version was for testing and internal use only, and not officially released.

Functionality Added or Changed

  • Important Change: The default value of the DiskIOThreadPool data node configuration parameter has changed from 8 to 2.

  • Cluster Replication: In circular replication, it was sometimes possible for an event to propagate such that it would be reapplied on all servers. This could occur when the originating server was removed from the replication circle and so could no longer act as the terminator of its own events, as normally happens in circular replication.

    To prevent this from occurring, a new IGNORE_SERVER_IDS option is introduced for the CHANGE MASTER TO statement. This option takes a list of replication server IDs; events having a server ID which appears in this list are ignored and not applied. For more information, see CHANGE MASTER TO Syntax.

    In conjunction with the introduction of IGNORE_SERVER_IDS, SHOW SLAVE STATUS has two new fields. Replicate_Ignore_Server_Ids displays information about ignored servers. Master_Server_Id displays the server_id value from the master. (Bug #47037)

    References: See also: Bug #25998, Bug #27808.

Bugs Fixed

  • Incompatible Change; Cluster API: Several NDB API methods were declared as const, but did not return an lvalue, which caused compiler warnings when using gcc 4.3 or newer to perform the build. The methods affected are NdbEventOperation::tableNameChanged(), NdbEventOperation::tableFrmChanged(), NdbEventOperation::tableFragmentationChanged(), NdbEventOperation::tableRangeListChanged(), and NdbOperation::getType(). (Bug #44840)

  • Important Change: The --with-ndb-port-base option for configure has been removed. It is now handled as an unknown and invalid option if you attempt to use it when configuring a build of MySQL Cluster. (Bug #47941)

    References: See also: Bug #38502.

  • The value set by the --ndb-cluster-connection-pool option was not shown in the output of SHOW STATUS LIKE 'NDB%'. (Bug #44118)

  • mysqld could sometimes crash during a commit while trying to handle NDB Error 4028 Node failure caused abort of transaction. (Bug #38577)

  • When building storage engines on Windows it was not possible to specify additional libraries within the CMake file required for the build. An ${engine}_LIBS macro has been included in the files to support these additional storage-engine specific libraries. (Bug #47797)

  • When building a pluggable storage engine on Windows, the engine name could be based on the directory name where the engine was located, rather than the configured storage engine name. (Bug #47795)

  • On OS X or Windows, sending a SIGHUP signal to the server or an asynchronous flush (triggered by flush_time) caused the server to crash. (Bug #47525)

  • The ARCHIVE storage engine lost records during a bulk insert. (Bug #46961)

  • When using the ARCHIVE storage engine, SHOW TABLE STATUS displayed incorrect information for Max_data_length, Data_length and Avg_row_length. (Bug #29203)

  • Installation of MySQL on Windows failed to set the correct location for the character set files, which could lead to mysqld and mysql failing to initialize properly. (Bug #17270)