MySQL Forums
Forum List  »  Announcements

MySQL Cluster 7.4.28 has been released
Posted by: Tvarita Jain
Date: April 28, 2020 04:08AM

Dear MySQL Users,

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

- In-Memory storage - Real-time performance
- 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.4 makes significant advances in performance;
operational efficiency (such as enhanced reporting and faster restarts
and upgrades) and conflict detection and resolution for active-active
replication between MySQL Clusters.

MySQL Cluster 7.4.28 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.4/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/


Changes in MySQL NDB Cluster 7.4.28 (5.6.48-ndb-7.4.28) (2020-04-28, General Availability)

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

Obtaining MySQL NDB Cluster 7.4. MySQL NDB Cluster 7.4
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.4, see
What is New in NDB Cluster 7.4
( https://dev.mysql.com/doc/refman/5.6/en/mysql-cluster-what-is-new-7-4.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.48 (see Changes in MySQL 5.6.48 (2020-04-27, General Availability)
( https://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-48.html )) .

* Functionality Added or Changed

* Bugs Fixed

Functionality Added or Changed


* NDB Client Programs: Removed a dependency from the
ndb_waiter and ndb_show_tables utility programs on the
NDBT library. This library, used in NDB development for
testing, is not required for normal use. The visible
effect for users from this change is that these programs
no longer print NDBT_ProgramExit - status following
completion of a run. Applications that depend upon this
behavior should be updated to reflect this change when
upgrading to this release.

* Added the --ndb-log-fail-terminate option for mysqld.
When used, this causes the SQL node to terminate if it is
unable to log all row events. (Bug #21911930)

Bugs Fixed


* When a node ID allocation request failed with NotMaster
temporary errors, the node ID allocation was always
retried immediately, without regard to the cause of the
error. This caused a very high rate of retries, whose
effects could be observed as an excessive number of Alloc
node id for node nnn failed log messages (on the order of
15,000 messages per second). (Bug #30293495)

* For NDB tables having no explicit primary key,
NdbReceiverBuffer could be allocated with too small a
size. This was due to the fact that the attribute bitmap
sent to NDB from the data nodes always includes the
primary key. The extra space required for hidden primary
keys is now taken into consideration in such cases. (Bug
#30183466)

On Behalf of MySQL Release Engineering Team,
Tvarita Jain

Options: ReplyQuote


Subject
Views
Written By
Posted
MySQL Cluster 7.4.28 has been released
1479
April 28, 2020 04:08AM


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.