What is New in NDB Cluster A collation provides its own hash function, which hashes the string directly without first creating a normalized string. In addition, for a Unicode 9.0 collation, the hash is computed without padding.  NDB now takes advantage of this built-in function whenever hashing a string identified as using a Unicode 9.0 collation. Since, for other collations, there are existing databases which are hash partitioned on the transformed string,  NDB  continues to employ the previous method for hashing strings that use these, to maintain compatibility. (Bug #89590, Bug #89604, Bug #89609, Bug #27515000, Bug #27523758, Bug #27522732) SHOW BINLOG EVENTS ,  FLUSH LOGS , and most data definition statements continue, as they did in previous  NDB  versions, to operate in a synchronous fashion. As part of this work, several new data node parameters controlling transactional resources in  DBTC , listed here, have been added: • ReservedConcurrentIndexOperations • ReservedConcurrentOperations • ReservedConcurrentScans • ReservedConcurrentTransactions • Dynamic transactional resource allocation.   Allocation of resources in the transaction corrdinator (see The DBTC Block) is now performed using dynamic memory pools. This means that resource allocation determined by data node configuration parameters such as  MaxDMLOperationsPerTransaction , MaxNoOfConcurrentIndexOperations ,  MaxNoOfConcurrentOperations , MaxNoOfConcurrentScans ,  MaxNoOfConcurrentTransactions ,  MaxNoOfFiredTriggers , MaxNoOfLocalScans , and  TransactionBufferMemory  is now done in such a way that, if the load represented by each of these parameters is within the target load for all such resources, others of these resources can be limited so as not to exceed the total resources available. • ndb_log_bin default.   Beginning with NDB 8.0.16, the default value of the  ndb_log_bin  system variable has changed from  TRUE  to  FALSE . • ndb_restore option usage.   Beginning with NDB 8.0.16, the  --nodeid  and  --backupid  options are both required when invoking  ndb_restore . • RESET MASTER changes.   Because the MySQL Server now executes  RESET MASTER  with a global read lock, the behavior of this statement when used with NDB Cluster has changed in the following two respects: •It is no longer guaranteed to be synonchrous; that is, it is now possible that a read coming immediately before  RESET MASTER  is issued may not be logged until after the binary log has been rotated. •Subsequent MD5 hashing consisted mainly of padding with spaces, and was not particularly efficient, possibly causing additional performance penalties by flushing significant portions of the L1 cache. •It now behaves in exactly the same fashion, whether the statement is issued on the same SQL node that is writing the binary log, or on a different SQL node in the same cluster. Note 3942