What is New in NDB Cluster done, you can update IPv4 addresses used in the  config.ini  file with IPv6 addresses. After this, to cause the configuration changes to take effect and to make the cluster start using the IPv6 addresses, it is necessary to perform a system restart of the cluster. • Auto-Installer deprecation and removal.   The MySQL NDB Cluster Auto-Installer web-based installation tool ( ndb_setup.py ) is deprecated in NDB 8.0.22, and is removed in NDB 8.0.23 and later. It is no longer supported. • ndbmemcache deprecation and removal.  ndbmemcache  is no longer supported.  ndbmemcache was deprecated in NDB 8.0.22, and removed in NDB 8.0.23. • ndbinfo backup_id table.   NDB 8.0.24 adds a  backup_id  table to the  ndbinfo  information database. This is intended to serve as a replacement for obtaining this information by using ndb_select_all  to dump the contents of the internal  SYSTAB_0  tyable, which is error-prone and takes an excessively long time to perform. • Table partitioning enhancements.   NDB 8.0.23 introduces a new method for handling table partitions and fragments, which can determine the number of local data managers (LDMs) for a given data node independently of the number of redo log parts. This means that the number of LDMs can now be highly variable.  NDB  can employ this method when the  ClassicFragmentation  data node configuration parameter, also implemented in NDB 8.0.23, is set to  false ; when this is the case, the number of LDMs is no longer used to determine how many partitions to create for a table per data node, and the value of the  PartitionsPerNode  parameter (also introduced in NDB 8.0.23) determines this number instead, which is also used for calculating the number of fragments used for a table. • Terminology updates.   To align with work begun in MySQL 8.0.21 and NDB 8.0.21, NDB 8.0.23 implements a number of changes in terminology, listed here: •The system variable  ndb_slave_conflict_role  is now deprecated. It is replaced by ndb_conflict_role . •Many  NDB  status variables are deprecated. These variables, and their replacements, are shown in the following table: This table has a single column and row containing the ID of the most recent backup of the cluster taken using the  START BACKUP  management client command. In the event that no backup of this cluster can be found, the table contains a single row whose column value is  0 . When  ClassicFragmentation  has its default value  true , then the traditional method of using the number of LDMs is used to determine the number of fragments that a table should have. For more information, see the descriptions of the new parameters referenced previously, in Multi- Threading Configuration Parameters (ndbmtd). Table 23.1 Deprecated NDB status variables and their replacements Deprecated variable Replacement Ndb_api_adaptive_send_deferred_count_slave Ndb_api_adaptive_send_deferred_count_replica Ndb_api_adaptive_send_forced_count_slave Ndb_api_adaptive_send_forced_count_replica Ndb_api_adaptive_send_unforced_count_slave Ndb_api_adaptive_send_unforced_count_replica Ndb_api_bytes_received_count_slave Ndb_api_bytes_received_count_replica Ndb_api_bytes_sent_count_slave Ndb_api_bytes_sent_count_replica Ndb_api_pk_op_count_slave Ndb_api_pk_op_count_replica Ndb_api_pruned_scan_count_slave Ndb_api_pruned_scan_count_replica 3952