MySQL Forums
Forum List  »  Announcements

MySQL Cluster 7.5.13 has been released
Posted by: Prashant Tekriwal
Date: January 22, 2019 07:19AM



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.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.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.13 (5.7.25-ndb-7.5.13) (
2019-01-22, General Availability)

   MySQL NDB Cluster 7.5.13 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
   ( http://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
( http://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.25 (see Changes in MySQL 5.7.25
   (2019-01-21, General Availability)
( http://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-25.html )).

Bugs Fixed

     * Important Change: When restoring to a cluster using data
       node IDs different from those in the original cluster,
       ndb_restore tried to open files corresponding to node ID
       0. To keep this from happening, the --nodeid
       ( http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-programs-ndb-restore.html#option_ndb_restore_nodeid )
        and --backupid
       ( http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-programs-ndb-restore.html#option_ndb_restore_backupid )
       options---neither of which has a default value---are both
       now explicitly required when invoking ndb_restore. (Bug#28813708)

     * Packaging; MySQL NDB ClusterJ: libndbclient was missing
       from builds on some platforms. (Bug #28997603)

     * NDB Replication: When writes on the master---done in such
       a way that multiple changes affecting BLOB
       ( http://dev.mysql.com/doc/refman/5.7/en/blob.html ) column
       values belonging to the same primary key were part of the
       same epoch---were replicated to the slave, Error 1022
       occurred due to constraint violations in the
       NDB$BLOB_id_part table. (Bug #28746560)

     * When only the management server but no data nodes were
       started, RESTART ALL timed out and eventually failed.
       This was because, as part of a restart, ndb_mgmd starts a
       timer, sends a STOP_REQ signal to all the data nodes, and
       waits for all of them to reach node state SL_CMVMI. The
       issue arose becaue no STOP_REQ signals were ever sent,
       and thus no data nodes reached SL_CMVMI. This meant that
       the timer always expired, causing the restart to fail.
       (Bug #28728485, Bug #28698831)
       References: See also: Bug #11757421.

     * Running ANALYZE TABLE
      ( http://dev.mysql.com/doc/refman/5.7/en/analyze-table.html )
       on an NDB table with an index having longer than the
       supported maximum length caused data nodes to fail. (Bug#28714864)

     * It was possible in certain cases for nodes to hang during
       an initial restart. (Bug #28698831)
       References: See also: Bug #27622643.

     * The output of ndb_config --configinfo
       ( http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-programs-ndb-config.html#option_ndb_config_configinfo )
        --xml ( http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-programs-ndb-config.html#option_ndb_config_xml )
       --query-all ( http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-programs-ndb-config.html#option_ndb_config_query-all )
       now shows that configuration changes for the ThreadConfig
       ( http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndbd-definition.html#ndbparam-ndbmtd-threadconfig )
       and MaxNoOfExecutionThreads ( http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndbd-definition.html#ndbparam-ndbmtd-maxnoofexecutionthreads )
       data node parameters require system initial restarts
       (restart="system" initial="true"). (Bug #28494286)

     * Executing SELECT
       ( http://dev.mysql.com/doc/refman/5.7/en/select.html ) *
       FROM INFORMATION_SCHEMA.TABLES
       ( http://dev.mysql.com/doc/refman/5.7/en/tables-table.html )
       caused SQL nodes to restart in some cases. (Bug#27613173)

     * When running a cluster with 4 or more data nodes under
       very high loads, data nodes could sometimes fail with
       Error 899 Rowid already allocated. (Bug #25960230)

     * When starting, a data node copies metadata, while a local
       checkpoint updates metadata. To avoid any conflict, any
       ongoing LCP activity is paused while metadata is being
       copied. An issue arose when a local checkpoint was paused
       on a given node, and another node that was also
       restarting checked for a complete LCP on this node; the
       check actually caused the LCP to be completed before
       copying of metadata was complete and so ended the pause
       prematurely. Now in such cases, the LCP completion check
       waits to complete a paused LCP until copying of metadata
       is finished and the pause ends as expected, within the
       LCP in which it began. (Bug #24827685)

     * Asynchronous disconnection of mysqld from the cluster
       caused any subsequent attempt to start an NDB API
       transaction to fail. If this occurred during a bulk
       delete operation, the SQL layer called
       HA::end_bulk_delete(), whose implementation by
       ha_ndbcluster assumed that a transaction had been
       started, and could fail if this was not the case. This
       problem is fixed by checking that the transaction pointer
       used by this method is set before referencing it. (Bug
       #20116393)

     * NdbScanFilter did not always handle NULL according to the
       SQL standard, which could result in sending
       non-qualifying rows to be filtered (otherwise not
       necessary) by the MySQL server. (Bug #92407, Bug#28643463)

     * NDB attempted to use condition pushdown on greater-than
       (>) and less-than (<) comparisons with ENUM
       ( http://dev.mysql.com/doc/refman/5.7/en/enum.html ) column
       values but this could cause rows to be omitted in the
       result. Now such comparisons are no longer pushed down.
       Comparisons for equality (=) and inequality (<> / !=)
       with ENUM values are not affected by this change, and
       conditions including these comparisons can still be
       pushed down. (Bug #92321, Bug #28610217)

On Behalf of Oracle/MySQL Release Engineering Team
Prashant Tekriwal

Options: ReplyQuote


Subject
Views
Written By
Posted
MySQL Cluster 7.5.13 has been released
935
January 22, 2019 07:19AM


Sorry, you do not have permission to post/reply in this forum.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.