The following sections describe changes in the implementation of MySQL NDB Cluster in NDB Cluster 9.0.1, as compared to earlier release series. NDB Cluster 9.0 is available as a Development release for preview and testing of new features currently under development. For production, please use NDB 8.4; for more information, see MySQL NDB Cluster 8.4. NDB Cluster 8.0, 7.6, and 7.5 are previous GA releases still supported in production, although we recommend that new deployments for production use MySQL NDB Cluster 8.4.
What is New in NDB Cluster 9.0
Major changes and new features in NDB Cluster 9.0 which are likely to be of interest are listed here:
NDB replication applier status table. NDB Cluster 9.0 adds a
ndb_replication_applier_status
table to the Performance Schema, providing per-channel information about the applier's status, including information relating to conflict detection and resolution. This table can be thought of as an NDB-specific extension to the existingreplication_applier_status
table.Previously, information about the NDB replication applier was available to the user only as a set of server status variables, which applied only to the default replication channel.
For more information, see Section 29.12.12.3, “The ndb_replication_applier_status Table”, as well as Section 25.7, “NDB Cluster Replication”.
Deprecation of Node.js.
Node.js
support in MySQL NDB Cluster is now deprecated, and you should expect its removal in a future release.You can also find the NDB Cluster
jones-ndb
driver forNode.js
athttps://github.com/mysql/mysql-js
, where it remains available to interested users.ndb_size.pl deprecated. The ndb_size.pl utility is deprecated in NDB 9.0.0 and later, and no longer supported. You can expect it to be removed from a future version of the NDB Cluster distribution.
MySQL Cluster Manager has an advanced command-line interface that can simplify many complex NDB Cluster management tasks. See MySQL Cluster Manager 9.0.1 User Manual, for more information.