Movatterモバイル変換

MySQL NDB Cluster uses the MySQL server with theNDB storage engine. Support for theNDB storage engine is not included in standard MySQL Server 5.7 binaries built by Oracle. Instead, users of NDB Cluster binaries from Oracle should upgrade to the most recent binary release of NDB Cluster for supported platforms—these include RPMs that should work with most Linux distributions. NDB Cluster users who build from source should use the sources provided for NDB Cluster. (Locations where the sources can be obtained are listed later in this section.)

Supported Platforms.  NDB Cluster is currently available and supported on a number of platforms. For exact levels of support available for on specific combinations of operating system versions, operating system distributions, and hardware platforms, please refer tohttps://www.mysql.com/support/supportedplatforms/cluster.html.

Availability.  NDB Cluster binary and source packages are available for supported platforms fromhttps://dev.mysql.com/downloads/cluster/.

NDB Cluster release numbers.  NDB Cluster follows a somewhat different release pattern from the mainline MySQL Server 5.7 series of releases. In thisManual and other MySQL documentation, we identify these and later NDB Cluster releases employing a version number that begins with“NDB”. This version number is that of theNDBCLUSTER storage engine used in the release, and not of the MySQL server version on which the NDB Cluster release is based.

Version strings used in NDB Cluster software.  The version string displayed by NDB Cluster programs uses this format:

mysql-mysql_server_version-ndb-ndb_engine_version

mysql_server_version represents the version of the MySQL Server on which the NDB Cluster release is based. For all NDB Cluster 7.5 and NDB Cluster 7.6 releases, this is“5.7”.ndb_engine_version is the version of theNDB storage engine used by this release of the NDB Cluster software. You can see this format used in themysql client, as shown here:

$> mysqlWelcome to the MySQL monitor.  Commands end with ; or \g.Your MySQL connection id is 2Server version: 5.7.44-ndb-7.5.36 Source distributionType 'help;' or '\h' for help. Type '\c' to clear the buffer.mysql> SELECT VERSION()\G*************************** 1. row ***************************VERSION(): 5.7.44-ndb-7.5.361 row in set (0.00 sec)

This version string is also displayed in the output of theSHOW command in thendb_mgm client:

ndb_mgm> SHOWConnected to Management Server at: localhost:1186Cluster Configuration---------------------[ndbd(NDB)]     2 node(s)id=1    @10.0.10.6  (5.7.44-ndb-7.5.36, Nodegroup: 0, *)id=2    @10.0.10.8  (5.7.44-ndb-7.5.36, Nodegroup: 0)[ndb_mgmd(MGM)] 1 node(s)id=3    @10.0.10.2  (5.7.44-ndb-7.5.36)[mysqld(API)]   2 node(s)id=4    @10.0.10.10  (5.7.44-ndb-7.5.36)id=5 (not connected, accepting connect from any host)

The version string identifies the mainline MySQL version from which the NDB Cluster release was branched and the version of theNDB storage engine used. For example, the full version string for NDB 7.5.4 (the first NDB 7.5 GA release) wasmysql-5.7.16-ndb-7.5.4. From this we can determine the following:

New NDB Cluster releases are numbered according to updates in theNDB storage engine, and do not necessarily correspond in a one-to-one fashion with mainline MySQL Server releases. For example, NDB 7.5.4 (as previously noted) was based on MySQL 5.7.16, while NDB 7.5.3 was based on MySQL 5.7.13 (version string:mysql-5.7.13-ndb-7.5.3).

Compatibility with standard MySQL 5.7 releases.  While many standard MySQL schemas and applications can work using NDB Cluster, it is also true that unmodified applications and database schemas may be slightly incompatible or have suboptimal performance when run using NDB Cluster (seeSection 21.2.7, “Known Limitations of NDB Cluster”). Most of these issues can be overcome, but this also means that you are very unlikely to be able to switch an existing application datastore—that currently uses, for example,MyISAM orInnoDB—to use theNDB storage engine without allowing for the possibility of changes in schemas, queries, and applications. In addition, the MySQL Server and NDB Cluster codebases diverge considerably, so that the standardmysqld cannot function as a drop-in replacement for the version ofmysqld supplied with NDB Cluster.

NDB Cluster development source trees.  NDB Cluster development trees can also be accessed fromhttps://github.com/mysql/mysql-server.

The NDB Cluster development sources maintained athttps://github.com/mysql/mysql-server are licensed under the GPL. For information about obtaining MySQL sources using Git and building them yourself, seeSection 2.8.5, “Installing MySQL Using a Development Source Tree”.

NDB Cluster 8.0 (GA) and NDB Cluster 8.4 (LTS), are recommended for new deployments; seeWhat is New in MySQL NDB Cluster 8.0, andWhat is New in MySQL NDB Cluster 8.4, respectively, for more information about these release series. NDB Cluster 9.3 is also available as an Innovation release (seeWhat is New in MySQL NDB Cluster 9.4). NDB Cluster 7.6 is a previous GA release still supported in production. NDB Cluster 7.5 and earlier are previous GA releases which are no longer maintained. We recommend that new deployments for production use MySQL NDB Cluster 8.0.

The contents of this chapter are subject to revision as NDB Cluster continues to evolve. Additional information regarding NDB Cluster can be found on the MySQL website athttp://www.mysql.com/products/cluster/.

Additional Resources.  More information about NDB Cluster can be found in the following places: