MySQL Cluster 7.6.9 has been released

2019-01-22 Thread Lars Tangvald 

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.6.9 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.6 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.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.9 (5.7.25-ndb-7.6.9) (2019-01-22, 
General Availability)


   MySQL NDB Cluster 7.6.9 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
(http://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.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 and
   --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: A DROP DATABASE operation involving
   certain very large tables could lead to an unplanned
   shutdown of the cluster. (Bug #28855062)

 * NDB Replication: When writes on the master---done in such
   a way that multiple changes affecting BLOB 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)

 * NDB Cluster APIs: When the NDB kernel's SUMA block sends
   a TE_ALTER event, it does not keep track of when all
   fragments of the event are sent. When NDB receives the
   event, it buffers the fragments, and processes the event
   when all fragments have arrived. An issue could possibly
   arise for very large table definitions, when the time
   between transmission and reception could span multiple
   epochs; during this time, SUMA could send a
   SUB_GCP_COMPLETE_REP signal to indicate that it has sent
   all data for an epoch, even though in this case that is
   not entirely true since there may be fragments of a
   TE_ALTER event still waiting on the data node to be sent.
   Reception of the SUB_GCP_COMPLETE_REP leads to closing
   the buffers for that epoch. Thus, when TE_ALTER finally
   arrives, NDB assumes that it is a duplicate from an
   earlier epoch, and silently discards it.
   We fix the problem by making sure that the SUMA kernel
   block never sends a SUB_GCP_COMPLETE_REP for any epoch in
   which there are unsent fragments for a SUB_TABLE_DATA
   signal.
   This issue could have an impact on NDB API applications
   making use of TE_ALTER events. (SQL nodes do not make any
   use of TE_ALTER events and so they and applications using
   them were not affected.) (Bug #28836474)

 * Where a data node was restarted after a configuration
   change whose result was a decrease in the sum of
   MaxNoOfTables, MaxNoOfOrderedIndexes, and
   MaxNoOfUniqueHashIndexes, it sometimes failed with a
   misleading

MySQL Cluster 7.5.13 has been released

2019-01-22 Thread Prashant Tekriwal 

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-pro 

grams-ndb-restore.html#option_ndb_restore_nodeid 
) 
and

   --backupid
   (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-pro 

grams-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-pro

MySQL Cluster 7.5.13 has been released

2019-01-22 Thread Prashant Tekriwal 

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-pro
   grams-ndb-restore.html#option_ndb_restore_nodeid) and
   --backupid
   (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-pro
   grams-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-pro
   grams-ndb-config.html#option_ndb_config_configinfo) --xml
   (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-pro
   grams-ndb-config.html#option_ndb_config_xml) --query-all
   (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-pro
   grams-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-ndb