MySQL Cluster 7.3.30 has been released

[Rafal Molenda]

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.3.30 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.3/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.3.30 (5.6.49-ndb-7.3.30) (2020-07-14, 
General Availability)

   MySQL NDB Cluster 7.3.30 is a new release of NDB Cluster,
   based on MySQL Server 5.6 and including features from version
   7.3 of the NDB storage engine, as well as fixing a number of
   recently discovered bugs in previous NDB Cluster releases.

   Obtaining MySQL NDB Cluster 7.3.  MySQL NDB Cluster 7.3
   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.3, see
   What is New in NDB Cluster 7.3
   (https://dev.mysql.com/doc/refman/5.6/en/mysql-cluster-what-is-new-7-3.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.6
   through MySQL 5.6.49 (see Changes in MySQL 5.6.49 (2020-07-13, 
   General Availability)
   (https://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-49.html)).


Bugs Fixed

     * During a node restart, the SUMA block of the node that is
       starting must get a copy of the subscriptions (events
       with subscribers) and subscribers (NdbEventOperation
       instances which are executing) from a node already
       running. Before the copy is complete, nodes which are
       still starting ignore any user-level SUB_START or
       SUB_STOP requests; after the copy is done, they can
       participate in such requests. While the copy operation is
       in progress, user-level SUB_START and SUB_STOP requests
       are blocked using a DICT lock.
       An issue was found whereby a starting node could
       participate in SUB_START and SUB_STOP requests after the
       lock was requested, but before it is granted, which
       resulted in unsuccessful SUB_START and SUB_STOP requests.
       This fix ensures that the nodes cannot participate in
       these requests until after the DICT lock has actually
       been granted. (Bug #31302657)

     * The Dojo toolkit included with NDB Cluster and used by
       the Auto-Installer was upgraded to version 1.15.3. (Bug
       #31029110)

     * When executing any of the SHUTDOWN, ALL STOP, or ALL
       RESTART management commands, it is possible for different
       nodes to attempt to stop on different global checkpoint
       index (CGI) boundaries. If they succeed in doing so, then
       a subsequent system restart is slower than normal because
       any nodes having an earlier stop GCI must undergo
       takeover as part of the process. When nodes failing on
       the first GCI boundary cause surviving nodes to be
       nonviable, surviving nodes suffer an arbitration failure;
       this has the positive effect of causing such nodes to
       halt at the correct GCI, but can give rise to spurious
       errors or similar.
       To avoid such issues, extra synchronization is now
       performed during a planned shutdown to reduce the
       likelihood that different data nodes attempt to shut down
       at different GCIs as well as the use of unnecessary node
       takeovers during system restarts. (Bug #31008713)
 

On Behalf of MySQL Release Engineering Team,
Rafal Molenda