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.10, 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.
MySQL Cluster 7.5 is also available from our repository for Linux
platforms, go here for details:
http://dev.mysql.com/downloads/repo/
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.10 (5.7.22-ndb-7.5.10) (2018-04-20,
General Availability)
MySQL NDB Cluster 7.5.10 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
http://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.22 (see Changes in MySQL 5.7.22 (2018-04-19,
General Availability)
(http://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-22.html)).
Bugs Fixed
* NDB Cluster APIs: A previous fix for an issue, in which
the failure of multiple data nodes during a partial
restart could cause API nodes to fail, did not properly
check the validity of the associated NdbReceiver object
before proceeding. Now in such cases an invalid object
triggers handling for invalid signals, rather than a node
failure. (Bug #25902137)
References: This issue is a regression of: Bug #25092498.
* NDB Cluster APIs: Incorrect results, usually an empty
result set, were returned when setBound()
(http://dev.mysql.com/doc/ndbapi/en/ndb-ndbindexscanoperation-setbound.html)
was used to specify a NULL bound.
This issue appears to have been caused by a problem in
gcc, limited to cases using the old version of this
method (which does not employ NdbRecord
(http://dev.mysql.com/doc/ndbapi/en/ndb-ndbrecord.html)),
and is fixed by rewriting the problematic internal logic
in the old implementation. (Bug #89468, Bug #27461752)
* In some circumstances, when a transaction was aborted in
the DBTC block, there remained links to trigger records
from operation records which were not yet
reference-counted, but when such an operation record was
released the trigger reference count was still
decremented. (Bug #27629680, Bug #27629680)
* ANALYZE TABLE
(http://dev.mysql.com/doc/refman/5.7/en/analyze-table.html)
used excessive amounts of CPU on large,
low-cardinality tables. (Bug #27438963)
* Queries using very large lists with IN were not handled
correctly, which could lead to data node failures. (Bug
#27397802)
* A data node overload could in some situations lead to an
unplanned shutdown of the data node, which led to all
data nodes disconnecting from the management and nodes.
This was due to a situation in which API_FAILREQ was not
the last received signal prior to the node failure.
As part of this fix, the transaction coordinator's
handling of SCAN_TABREQ signals for an ApiConnectRecord
in an incorrect state was also improved. (Bug #27381901)
References: See also: Bug #47039, Bug #11755287.
* In a two-node cluster, when the node having the lowest ID
was started using --nostart
(http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-programs-ndbd.html#option_ndbd_nostart),
API clients could
not connect, failing with Could not alloc node id at HOST
port PORT_NO: No free node id found for mysqld(API). (Bug
#27225212)
* Race conditions sometimes occurred during asynchronous
disconnection and reconnection of the transporter while
other threads concurrently inserted signal data into the
send buffers, leading to an unplanned shutdown of the
cluster.
As part of the work fixing this issue, the internal
templating function used by the Transporter Registry when
it prepares a send is refactored to use
likely-or-unlikely logic to speed up execution, and to
remove a number of duplicate checks for NULL. (Bug
#24444908, Bug #25128512)
References: See also: Bug #20112700.
* ndb_restore sometimes logged data file and log file
progress values much greater than 100%. (Bug #20989106)
* As a result of the reuse of code intended for send
threads when performing an assist send, all of the local
release send buffers were released to the global pool,
which caused the intended level of the local send buffer
pool to be ignored. Now send threads and assisting worker
threads follow their own policies for maintaining their
local buffer pools. (Bug #89119, Bug #27349118)
* When sending priority A signals, we now ensure that the
number of pending signals is explicitly initialized. (Bug
#88986, Bug #27294856)
* ndb_restore --print_data
(http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-programs-ndb-restore.html#option_ndb_restore_print_data)
--hex
(http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-programs-ndb-restore.html#option_ndb_restore_hex)
did not print trailing 0s of LONGVARBINARY
(http://dev.mysql.com/doc/refman/5.7/en/blob.html)
values. (Bug #65560, Bug #14198580)
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql
