MySQL Forums
Forum List  »  Announcements

MySQL Cluster 7.6.18 has been released
Posted by: Sreedhar Sreedhargadda
Date: April 21, 2021 03:16AM

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 and http)
 
MySQL Cluster 7.6.18 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.6/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.6.18 (5.7.34-ndb-7.6.18) (2021-04-21, General Availability)
 
   MySQL NDB Cluster 7.6.18 is a new release of NDB 7.6, based
   on MySQL Server 5.7 and including features in version 7.6 of
   the NDB storage engine, as well as fixing recently discovered
   bugs in previous NDB Cluster releases.
 
   Obtaining NDB Cluster 7.6.  NDB Cluster 7.6 source code and
   binaries can be obtained from
   https://dev.mysql.com/downloads/cluster/.
 
   For an overview of changes made in NDB Cluster 7.6, see What
   is New in NDB Cluster 7.6
   (https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-what-is-new-7-6.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.34 (see Changes in MySQL 5.7.34
   (2021-04-20, General Availability)
   (https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-34.html)).
 
Bugs Fixed 
 
     * ndb_mgmd now exits gracefully in the event of a SIGTERM
       just as it does following a management client SHUTDOWN
       command. (Bug #32446105)
 
     * Running out of disk space while performing an NDB backup
       could lead to an unplanned shutdown of the cluster. (Bug
       #32367250)
 
     * The default number of partitions per node (shown in
       ndb_desc output as PartitionCount) is calculated using
       the lowest number of LDM threads employed by any single
       live node, and was done only once, even after data nodes
       left or joined the cluster, possibly with a new
       configuration changing the LDM thread count and thus the
       default partition count. Now in such cases, we make sure
       the default number of partitions per node is recalculated
       whenever data nodes join or leave the cluster. (Bug
       #32183985)
 
     * The local checkpoint (LCP) mechanism was changed in NDB
       7.6 such that it also detected idle fragments---that is,
       fragments which had not changed since the last LCP and
       thus required no on-disk metadata update. The LCP
       mechanism could then immediately proceed to handle the
       next fragment. When there were a great many such idle
       fragments, the CPU consumption required merely to loop
       through these became highly significant, causing latency
       spikes in user transactions.
       A 1 ms delay was already inserted between each such idle
       fragment being handled. Testing later showed this to be
       too short an interval, and that we are normally not in as
       great a hurry to complete these idle fragments as we
       previously believed.
       This fix extends the idle fragment delay time to 20 ms if
       there are no redo alerts indicating an urgent need to
       complete the LCP. In case of a low redo alert state we
       wait 5 ms instead, and for a higher alert state we fall
       back to the 1 ms delay. (Bug #32068551)
       References: See also: Bug #31655158, Bug #31613158.
 
     * Calculation of the redo alert state based on redo log
       usage was overly aggressive, and thus incorrect, when
       using more than 1 log part per LDM.
 
On Behalf of the MySQL Engineering Team,
Sreedhar S


Options: ReplyQuote


Subject
Views
Written By
Posted
MySQL Cluster 7.6.18 has been released
403
April 21, 2021 03:16AM


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.