What is New in MySQL NDB Cluster 8.0.20

InnoDB, MySQL, MySQL 8, MySQL NDB Cluster, NDB Cluster

MySQL NDB Cluster 8.0.20 new features 

This post is about changes in the implementation of NDB Cluster from MySQL NDB Cluster 8.0 through 8.0.20, as compared to earlier release series. We have included only those of MySQL NDB Cluster 8.0.20 new features which are really interesting and can directly influence / make an impact to performance, scalability and reliability:

  • MySQL NDB Cluster  development is in parallel with the development of  MySQL Server going forward. What does that mean for MySQL customers globally NDB 8.0 is developed in, built from, and released with the MySQL 8.0 source code tree and numbering scheme for NDB Cluster 8.0 releases follows the scheme for MySQL 8.0 ( starting with version 8.0.13).
  • As of NDB 8.0.18, The identifiers can use up to 64 bytes for databases and tables (the 63-byte limit on identifiers is removed ).
  • Generated names for foreign keys similar to the patterns used by InnoDB – NDB version 8.0.18 and later uses the pattern tbl_name_fk_N
  • Responsive schema and metadata distribution and synchronization – MySQL NDB 8.0 (version 8.0.18 and later) will now use MySQL data dictionary to distribute schema information to SQL nodes joining a cluster and to synchronize new schema changes between existing SQL nodes.
  • More metadata information for intuitive troubleshooting and monitoring – Rather than storing the binary representation of the table as in previous NDB versions, The NDB 8.0.14 and later now use serialized metadata from the MySQL data dictionary (You can read more about MySQL Data Dictionary here ). This also means that NDB tables created in NDB Cluster 8.0.14 and later are not compatible with previous NDB Cluster releases.
  • On-the-fly upgrades from NDB 7.6 to NDB 8.0 – The compressed .frm file created from NDB 7.6 is no longer supported in MySQL 8.0. The upgrade is made simpler by on-the-fly translation of this metadata and writes it into the MySQL Server’s data dictionary, which enables the mysqld in NDB Cluster 8.0 to work with the table without preventing subsequent use of the table by a previous version of the NDBsoftware.
  • NDB_STORED_USER privilege for user privileges Synchronization – User roles and privileges can be synchronized across all SQL nodes in the cluster by issuing a GRANT NDB_STORED_USER statement.  A user or role having NDB_STORED_USER, along with its privileges, is shared with all SQL nodes as soon as they join a given NDB Cluster. The changes to the privileges of the user or role are synchronized immediately with all connected SQL nodes. It is possible to make such changes from any connected SQL node, but recommended practice is to do so from a designated SQL node only, since the order of execution of statements affecting privileges from different SQL nodes cannot be guaranteed to be the same on all SQL nodes.
  • What’s new with MySQL NDB 8.0 INFORMATION_SCHEMA ?
    • INFORMATION_SCHEMA tables are now populated with tablespace statistics for MySQL Cluster tables.
    • Tablespaces and log file groups are no longer represented in the FILES table.
  • Troubleshoot NDB Cluster error with ndb_perror – To know more details about NDB Cluster error codes and troubleshoot use ndb_perror  
  • Maximum row size for NDB Cluster increased:
    • NDB 8.0.18 increases the maximum number of bytes that can be stored in an NDBCLUSTER table from 14000 to 30000 bytes.
    • The maximum offset for a fixed-width column of an NDB table is 8188 bytes (unchanged from releases previous to 8.0.18).
    • The maximum size of a BLOB or TEXT column is 264 bytes (unchanged from releases previous to 8.0.18).
  • Rename NDB Cluster table columns online – Beginning with MySQL NDB Cluster 8.0.18, The columns of NDB tables can be renamed online, using ALGORITHM=INPLACE.
  • The offline ordered index builds are now multithreaded by default from MySQL NDB Cluster 8.0.18,  This improve restart and restore times and performance, availability, and the user experience compared to index rebuild which used to consume all cores available. The default value for BuildIndexThreads is changed from 0 to 128.
  • MySQL NDB Cluster 8.0.18 support more nodes – NDB 8.0.18 increases the maximum number of data nodes supported per cluster to 144 (previously, this was 48). Data nodes can now use node IDs in the range 1 to 144, inclusive.
  • NDB 8.0.19 makes the following changes in configuration parameter maximum and default values:
  • Tuning disk I/O for better NDB 8.0.19 performance:
    • Parameters introduced with NDB 8.0.19:
      • MaxDiskDataLatency – To manage degree of latency permitted for disk access and causes transactions taking longer than this length of time to be aborted.
      • DiskDataUsingSameDisk – Distribute disk I/O by benefitting from the advantage of housing Disk Data tablespaces on separate disks by increasing the rate at which checkpoints of such tablespaces can be performed.
    • Metadata available on ndbinfo database to monitor NDB 8.0.19 disk I/O performance:
      • Monitor write throughput performance from diskstat 
      • Monitor writes to Disk Data tablespaces for each of the last 20 seconds from diskstats_1sec
      • Monitor latency of disk operations relating to Disk Data tablespaces from pgman_time_track_stats
  • Read from any replicas supported from NDB 8.0.19 – This means default value for ndb_read_backup system variable is now ON. The value of the NDB_TABLE comment option READ_BACKUP is 1 when creating a new NDB table. Enabling read from any replica significantly improves performance for reads from NDB tables, with minimal impact on writes.

☛ MinervaDB contacts for MySQL NDB Cluster Consulting, Support and Remote DBA Services

Business FunctionContact
☎ CONTACT GLOBAL SALES (24*7)📞 (844) 588-7287 (USA)
📞 (415) 212-6625 (USA)
📞 (778) 770-5251 (Canada)
☎ TOLL FREE PHONE (24*7)📞 (844) 588-7287
🚩 MINERVADB FAX+1 (209) 314-2364
📨 MinervaDB Email - General / Sales / Consultingcontact@minervadb.com
📨 MinervaDB Email - Support support@minervadb.com
📨 MinervaDB Email -Remote DBAremotedba@minervadb.com
📨 Shiv Iyer Email - Founder and Principal shiv@minervadb.com
🏠 CORPORATE ADDRESS: CALIFORNIAMinervaDB Inc.,
340 S LEMON AVE #9718
WALNUT 91789 CA, US
🏠 CORPORATE ADDRESS: DELAWAREMinervaDB Inc.,
PO Box 2093 PHILADELPHIA PIKE #3339
CLAYMONT, DE 19703
🏠 CORPORATE ADDRESS: HOUSTON MinervaDB Inc., 1321 Upland Dr. PMB 19322, Houston,
TX 77043, US
About MinervaDB Corporation 88 Articles
Independent and vendor neutral consulting, support, remote DBA services and training for MySQL, MariaDB, Percona Server, PostgreSQL and ClickHouse with core expertize in performance, scalability and high availability . We are an virtual corporation, all of us work from home on multiple timezones and stay connected via Email, Skype, Google Hangouts, Phone and IRC supporting over 250 customers worldwide
Contact: Website Facebook Twitter

MySQL, InnoDB and Oracle are registered trademarks of Oracle Corp. MariaDB is a trademark of Monty Program AB. All other trademarks are property of their respective owners. Other product or company names mentioned may be trademarks or trade names of their respective owner. Copyrights © 2010-2022 All Rights Reserved by MinervaDB®.

UA-155183614-1