MySQL Cluster 7.3.13 has been released

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.13, 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 Cluster NDB 7.3.13 (5.6.29-ndb-7.3.13) (2016-04-18)

    MySQL Cluster NDB 7.3.13 is a new release of MySQL 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 MySQL Cluster releases.

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

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


    This release also incorporates all bugfixes and changes made
    in previous MySQL Cluster releases, as well as all bugfixes
    and feature changes which were added in mainline MySQL 5.6
    through MySQL 5.6.29 (see Changes in MySQL 5.6.29
    (2016-02-05)
    (http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-29.html)).

    Bugs Fixed

      * During node failure handling, the request structure used
        to drive the cleanup operation was not maintained
        correctly when the request was executed. This led to
        inconsistencies that were harmless during normal
        operation, but these could lead to assertion failures
        during node failure handling, with subsequent failure of
        additional nodes. (Bug #22643129)

      * The previous fix for a lack of mutex protection for the
        internal TransporterFacade::deliver_signal() function was
        found to be incomplete in some cases. (Bug #22615274)
        References: This bug was introduced by Bug #77225, Bug
        #21185585.

      * When setup of the binary log as an atomic operation one
        one SQL node failed, this could trigger a state in other
        SQL nodes in which they appeared to detect the SQL node
        participating in schema change distribution, whereas it
        had not yet completed binary log setup. This could in
        turn cause a deadlock on the global metadata lock when
        the SQL node still retrying binary log setup needed this
        lock, while another mysqld had taken the lock for itself
        as part of a schema change operation. In such cases, the
        second SQL node waited for the first one to act on its
        schema distribution changes, which it was not yet able to
        do. (Bug #22494024)

      * Duplicate key errors could occur when ndb_restore was run
        on a backup containing a unique index. This was due to
        the fact that, during restoration of data, the database
        can pass through one or more inconsistent states prior to
        completion, such an inconsistent state possibly having
        duplicate values for a column which has a unique index.
        (If the restoration of data is preceded by a run with
        --disable-indexes and followed by one with
        --rebuild-indexes, these errors are avoided.)
        Added a check for unique indexes in the backup which is
        performed only when restoring data, and which does not
        process tables that have explicitly been excluded. For
        each unique index found, a warning is now printed. (Bug
        #22329365)

      * Restoration of metadata with ndb_restore -m occasionally
        failed with the error message Failed to create index...
        when creating a unique index. While disgnosing this
        problem, it was found that the internal error
        PREPARE_SEIZE_ERROR (a temporary error) was reported as
        an unknown error. Now in such cases, ndb_restore retries
        the creation of the unique index, and PREPARE_SEIZE_ERROR
        is reported as NDB Error 748 Busy during read of event
        table. (Bug #21178339)
        References: See also Bug #22989944.

      * Optimization of signal sending by buffering and sending
        them periodically, or when the buffer became full, could
        cause SUB_GCP_COMPLETE_ACK signals to be excessively
        delayed. Such signals are sent for each node and epoch,
        with a minimum interval of TimeBetweenEpochs; if they are
        not received in time, the SUMA buffers can overflow as a
        result. The overflow caused API nodes to be disconnected,
        leading to current transactions being aborted due to node
        failure. This condition made it difficult for long
        transactions (such as altering a very large table), to be
        completed. Now in such cases, the ACK signal is sent
        without being delayed. (Bug #18753341)

      * Cluster API: Executing a transaction with an
        NdbIndexOperation based on an obsolete unique index
        caused the data node process to fail. Now the index is
        checked in such cases, and if it cannot be used the
        transaction fails with an appropriate error. (Bug #79494,
        Bug #22299443)

-- 
MySQL Announce Mailing List
For list archives: http://lists.mysql.com/announce
To unsubscribe:    http://lists.mysql.com/announce