MySQL Cluster 7.5.15 has been released

[Sreedhar Sreedhargadda]

 Dear MySQL Users,

MySQL Cluster is the distributed, shared-nothing variant of MySQL.
This storage engine provides:

  - In-Memory storage - Real-time performance (with optional
    checkpointing to disk)
  - Transparent Auto-Sharding - Read & write scalability
  - Active-Active/Multi-Master geographic replication

  - 99.999% High Availability with no single point of failure
    and on-line maintenance
  - NoSQL and SQL APIs (including C++, Java, http, Memcached
    and JavaScript/Node.js)

MySQL Cluster 7.5.15 has been released and can be downloaded from

  http://www.mysql.com/downloads/cluster/

where you will also find Quick Start guides to help you get your
first MySQL Cluster database up and running.

The release notes are available from

  http://dev.mysql.com/doc/relnotes/mysql-cluster/7.5/en/index.html

MySQL Cluster enables users to meet the database challenges of next
generation web, cloud, and communications services with uncompromising
scalability, uptime and agility.

More details can be found at

  http://www.mysql.com/products/cluster/

Enjoy !

==============================================================================
Changes in MySQL NDB Cluster 7.5.15 (5.7.27-ndb-7.5.15) (2019-07-23,
General Availability)

   MySQL NDB Cluster 7.5.15 is a new release of MySQL NDB
   Cluster 7.5, based on MySQL Server 5.7 and including features
   in version 7.5 of the NDB
   (https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster.html)
   storage engine, as well as fixing recently discovered bugs in
   previous NDB Cluster releases.

   Obtaining MySQL NDB Cluster 7.5.  MySQL NDB Cluster 7.5
   source code and binaries can be obtained from
   https://dev.mysql.com/downloads/cluster/.

   For an overview of changes made in MySQL NDB Cluster 7.5, see
   What is New in NDB Cluster 7.5
   (https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-what-is-new-7-5.html).

   This release also incorporates all bug fixes and changes made
   in previous NDB Cluster releases, as well as all bug fixes
   and feature changes which were added in mainline MySQL 5.7
   through MySQL 5.7.27 (see Changes in MySQL 5.7.27 (Not yet
   released, 2019-07-23)
   (https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-27.html)).

Functionality Added or Changed

     * Building with CMake3 is now supported by the
       compile-cluster script included in the NDB source
       distribution.

Bugs Fixed

     * Important Change: The dependency of ndb_restore on the
       NDBT library, which is used for internal testing only,
       has been removed. This means that the program no longer
       prints NDBT_ProgramExit: ... when terminating.
       Applications that depend upon this behavior should be
       updated to reflect this change when upgrading to this
       release.

     * NDB Replication: NDB did not handle binary logging of
       virtual generated columns of type BLOB
       (https://dev.mysql.com/doc/refman/5.7/en/blob.html)
       correctly. Now such columns are always regarded as having
       zero length.

     * The requestInfo fields for the long and short forms of
       the LQHKEYREQ signal had diffferent definitions; bits
       used for the key length in the short version were reused
       for flags in the long version, since the key length is
       implicit in the section length of the long version of the
       dignal but it was possible for long LQHKEYREQ signals to
       contain a keylength in these same bits, which could be
       misinterpreted by the receiving local query handler,
       potentially leading to errors. Checks have now been
       implemented to make sure that this no longer happens.
       (Bug #29820838)

     * Long TCKEYREQ signals did not always use the expected
       format when invoked from TCINDXREQ processing. (Bug
       #29772731)

     * Improved error message printed when the maximum offset
       for a FIXED column is exceeded. (Bug #29714670)

     * Data nodes could fail due to an assert in the DBTC block
       under certain circumstances in resource-constrained
       environments. (Bug #29528188)

     * When restoring TINYBLOB
       (https://dev.mysql.com/doc/refman/5.7/en/blob.html)
       columns, ndb_restore now treats them as having the BINARY
       character set. (Bug #29486538)

     * Restoration of epochs by ndb_restore failed due to
       temporary redo errors. Now ndb_restore retries epoch
       updates when such errors occur. (Bug #29466089)

     * ndb_restore --restore-epoch
       (https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-programs-ndb-restore.html#option_ndb_restore_restore-epoch)
       incorrectly reported the stop GCP as 1 less than the
       actual position. (Bug #29343655)

     * Added support which was missing in ndb_restore for
       conversions between the following sets of types:

          + BLOB
            (https://dev.mysql.com/doc/refman/5.7/en/blob.html)
            and BINARY
            (https://dev.mysql.com/doc/refman/5.7/en/binary-varbinary.html)
            or VARBINARY
            (https://dev.mysql.com/doc/refman/5.7/en/binary-varbinary.html)
            columns

          + TEXT
            (https://dev.mysql.com/doc/refman/5.7/en/blob.html)
            and BLOB columns

          + BLOB columns with unequal lengths

          + BINARY and VARBINARY columns with unequal lengths
       (Bug #28074988)

     * Restore points in backups created with the SNAPSHOTSTART
       option (see Using The NDB Cluster Management Client to
       Create a Backup
       (https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-backup-using-management-client.html))
       were not always consistent with epoch boundaries.
       (Bug #27566346) References: See also: Bug #27497461.


Enjoy and thanks for the support!

On Behalf of MySQL/ORACLE RE Team
Sreedhar S