MySQL Cluster 7.6.10 has been released
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.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.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.10 (5.7.26-ndb-7.6.10) (2019-04-26, General Availability) MySQL NDB Cluster 7.6.10 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.26 (see Changes in MySQL 5.7.26 (2019-04-25, General Availability) (http://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-26.html)). Bugs Fixed * NDB Disk Data: The error message returned when validation of MaxNoOfOpenFiles in relation to InitialNoOfOpenFiles failed has been improved to make the nature of the problem clearer to users. (Bug #28943749) * NDB Disk Data: Repeated execution of ALTER TABLESPACE ... ADD DATAFILE against the same tablespace caused data nodes to hang and left them, after being killed manually, unable to restart. (Bug #22605467) * NDB Cluster APIs: NDB now identifies short-lived transactions not needing the reduction of lock contention provided by NdbBlob::close() and no longer invokes this method in cases (such as when autocommit is enabled) in which unlocking merely causes extra work and round trips to be performed prior to committing or aborting the transaction. (Bug #29305592) References: See also: Bug #49190, Bug #11757181. * NDB Cluster APIs: When the most recently failed operation was released, the pointer to it held by NdbTransaction became invalid and when accessed led to failure of the NDB API application. (Bug #29275244) * When a pushed join executing in the DBSPJ block had to store correlation IDs during query execution, memory for these was allocated for the lifetime of the entire query execution, even though these specific correlation IDs are required only when producing the most recent batch in the result set. Subsequent batches require additional correlation IDs to be stored and allocated; thus, if the query took sufficiently long to complete, this led to exhaustion of query memory (error 20008). Now in such cases, memory is allocated only for the lifetime of the current result batch, and is freed and made available for re-use following completion of the batch. (Bug #29336777) References: See also: Bug #26995027. * API and data nodes running NDB 7.6 and later could not use an existing parsed configuration from an earlier release series due to being overly strict with regard to having values defined for configuration parameters new to the later release, which placed a restriction on possible upgrade paths. Now NDB 7.6 and later are less strict about having all new parameters specified explicitly in the configuration which they are served, and use hard-coded default values in such cases. (Bug #28993400) * Added DUMP 406 (NdbfsDumpRequests) to provide NDB file system information to global checkpoint and local checkpoint stall reports in the node logs. (Bug #28922609) * A race condition between the DBACC and D
MySQL Cluster 7.4.24 has been released
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.24 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/ Enjoy ! == Changes in MySQL NDB Cluster 7.4.24 (5.6.44-ndb-7.4.24) (2019-04-26, General Availability) MySQL NDB Cluster 7.4.24 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 (http://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.44 (see Changes in MySQL 5.6.44 (2019-04-25, General Availability) (http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-44.html)). Functionality Added or Changed * Building with CMake3 is now supported by the compile-cluster script included in the NDB source distribution. Bugs Fixed * When a pushed join executing in the DBSPJ block had to store correlation IDs during query execution, memory for these was allocated for the lifetime of the entire query execution, even though these specific correlation IDs are required only when producing the most recent batch in the result set. Subsequent batches require additional correlation IDs to be stored and allocated; thus, if the query took sufficiently long to complete, this led to exhaustion of query memory (error 20008). Now in such cases, memory is allocated only for the lifetime of the current result batch, and is freed and made available for re-use following completion of the batch. (Bug #29336777) References: See also: Bug #26995027. * In some cases, one and sometimes more data nodes underwent an unplanned shutdown while running ndb_restore. This occurred most often, but was not always restircted to, when restoring to a cluster having a different number of data nodes from the cluster on which the original backup had been taken. The root cause of this issue was exhaustion of the pool of SafeCounter objects, used by the DBDICT kernel block as part of executing schema transactions, and taken from a per-block-instance pool shared with protocols used for NDB event setup and subscription processing. The concurrency of event setup and subscription processing is such that the SafeCounter pool can be exhausted; event and subscription processing can handle pool exhaustion, but schema transaction processing could not, which could result in the node shutdown experienced during restoration. This problem is solved by giving DBDICT schema transactions an isolated pool of reserved SafeCounters which cannot be exhausted by concurrent NDB event activity. (Bug #28595915) * ndb_restore did not restore autoincrement values correctly when one or more staging tables were in use. As part of this fix, we also in such cases block applying of the SYSTAB_0 backup log, whose content continued to be applied directly based on the table ID, which could ovewrite the autoincrement values stored in SYSTAB_0 for unrelated tables. (Bug #27917769, Bug #27831990) References:
MySQL Cluster 7.6.9 has been released
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 mislea
MySQL Cluster 7.5.13 has been released
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 <http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-programs-ndb-restore.html#option_ndb_restore_nodeid> grams-ndb-restore.html#option_ndb_restore_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-pro <http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-programs-ndb-restore.html#option_ndb_restore_backupid> grams-ndb-restore.html#option_ndb_restore_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-pro <http://dev.my
MySQL Cluster 7.5.13 has been released
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
MySQL Cluster Manager 1.4.7 has been released
Dear MySQL Users,
MySQL Cluster Manager 1.4.7 can be downloaded from
the My Oracle Support (MOS) website. It will also be available
on Oracle Software Delivery Cloud at http://edelivery.oracle.com
<http://edelivery.oracle.com>with
the next monthly update
MySQL Cluster Manager is an optional component of the MySQL Cluster Carrier
Grade Edition, providing a command-line interface that automates common
management tasks, including the following online operations:
- Configuring and starting MySQL Cluster
- Upgrades
- Adding and removing cluster nodes
- Adding and removing site hosts
- Configuration changes
- Backup and restore
MySQL Cluster Manager is a commercial extension to the MySQL family of
products.
More details can be found at http://www.mysql.com/products/cluster/mcm/.
A brief summary of changes in MySQL Cluster Manager version 1.4.7 is
listed below:
Changes in MySQL Cluster Manager 1.4.7 (2018-12-14)
* Functionality Added or Changed
* Bugs Fixed
*Functionality Added or Changed*
* Agent: Performance has been improved for the add package
command by removing unnecessary queries from its
execution process. (Bug #28950231)
* Agent: The initialization script for mcmd now cleans up
the temporary files it creates under the tmp directory while
starting new mcmd processes. (Bug #28924059)
* Agent: The list hosts command now returns, in addition to
Available and Unavailable, two more possible statuses for
the agent of a host:
+ Recovery: The agent is in the process of recovering
itself
+ Unresponsive: The agent rejected an attempt to
connect
(Bug #28438155)
* Agent: The option --core-file
(http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-program-options-common.html#option_ndb_common_core-file),
when used at the command line to start a node in a wild
cluster, now causes the import cluster and update process
commands to give a warning (that the option "may be
removed on next restart of the process"), instead of
causing the commands to fail. See Creating and
Configuring the Target Cluster
(http://dev.mysql.com/doc/mysql-cluster-manager/1.4/en/mcm-using-import-cluster-create-configure.html)
for details. (Bug #28177366)
* Agent: The import cluster and update process commands now
support a new --remove-angel option, which kills any
angel processes for the data nodes to be imported or
updated and also updates the data nodes' PID files. See
descriptions for the two commands for details. (Bug
#28116279)
* Agent: The backup cluster command finishes faster now, as
some unnecessary wait time has been eliminated from the
backup process. (Bug #27986443)
* Agent: A new option for mcmd, --initial, allows an agent
that has fallen into an inconsistent state to recover its
configuration from other agents. See the description for
--initial for details. (Bug #20892397)
* Agent: The set, get, and reset commands now support the
following command-line-only attributes, which can only be
configured at the command line when outside MySQL Cluster
Manager:
+ For ndb_mgmd: --core-file, --log-name, --verbose
+ For ndbd and ndbmtd: --core-file, -- --verbose
* Agent: The internal mechanism for agent recovery
(http://dev.mysql.com/doc/mysql-cluster-manager/1.4/en/mcm-using-restore-agent.html)
has been improved, making it more robust and less error-prone.
* Client: To reduce the size of the mcmd log, node events
are no longer dumped into the log during a cluster
restart. (Bug #28843656)
* Client: The message for ERROR 5200 ("Restore cannot be
performed ...") has been expanded to include the reason
for the restore's failure. (Bug #25075284)
* Client: The message for ERROR 5017 has been expanded to
include the reason for an action being invalid for a
process or cluster. (Bug #22777846)
*Bugs Fixed*
* Agent: During a rolling restart for a cluster (which
takes place, for example, after a cluster
reconfiguration), the node group IDs for some data nodes
might become some invalid numbers transiently, and that
might cause mcmd to throw an internal error (Error 1003).
With this fix, such transient changes of node group IDs
are ignored by mcmd, and no error is thrown. (Bug
#28949173)
* Agent: An update process command on a mysqld node failed
with a timeout if the node was in the status of stopping.
It was because mcmd did not retry stopping the node, and
this fix makes it do so in the situation. (Bug #28913525)
* Agent: After a cluster reconfiguration failed, the
restart of an mcmd agent that had lost contac
MySQL Cluster 7.6.8 has been released
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.8, 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.8 (5.7.24-ndb-7.6.8) (2018-10-23,
General Availability)
MySQL NDB Cluster 7.6.8 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.24 (see Changes in MySQL 5.7.24 (2018-10-22,
General Availability)
(http://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-24.html)).
Functionality Added or Changed
* Performance: This release introduces a number of
significant improvements in the performance of scans;
these are listed here:
+ Row checksums help detect hardware issues, but do so
at the expense of performance. NDB now offers the
possibility of disabling these by setting the new
ndb_row_checksum server system variable to 0; doing
this means that row checksums are not used for new
or altered tables. This can have a significant
impact (5 to 10 percent, in some cases) on
performance for all types of queries. This variable
is set to 1 by default, to provide compatibility
with the previous behavior.
+ A query consisting of a scan can execute for a
longer time in the LDM threads when the queue is not
busy.
+ Previously, columns were read before checking a
pushed condition; now checking of a pushed condition
is done before reading any columns.
+ Performance of pushed joins should see significant
improvement when using range scans as part of join
execution.
Bugs Fixed
* Packaging: Expected NDB header files were in the devel
RPM package instead of libndbclient-devel. (Bug #84580,
Bug #26448330)
* NDB Disk Data: While restoring a local checkpoint, it is
possible to insert a row that already exists in the
database; this is expected behavior which is handled by
deleting the existing row first, then inserting the new
copy of that row. In some cases involving data on disk,
NDB failed to delete the existing row. (Bug #91627, Bug
#28341843)
* NDB Client Programs: Removed a memory leak in
NdbImportUtil::RangeList that was revealed in ASAN
builds. (Bug #91479, Bug #28264144)
* MySQL NDB ClusterJ: When a table containing a BLOB or a
TEXT field was being queried with ClusterJ for a record
that did not exist, an exception ("The method is not
valid in current blob state") was thrown. (Bug #28536926)
* MySQL NDB ClusterJ: A NullPointerException was thrown
when a full table scan was performed with ClusterJ on
tables containing either a BLOB or a TEXT field. It was
because the proper object initializations were omitted,
and they have now been added by this fix. (Bug #28199372,
Bug #91242)
* When copying deleted rows from a live node to a node just
starting, it is possible for one or more of these rows to
have a global checkpoint index equal to zero. If this
happened at the same time that a full lo
MySQL Cluster 8.0.13-dmr has been released
Dear MySQL Users, MySQL Cluster is the distributed database combining massive scalability and high availability. It provides in-memory real-time access with transactional consistency across partitioned and distributed datasets. It is designed for mission critical applications. MySQL Cluster has replication between clusters across multiple geographical sites built-in. A shared nothing architecture with data locality awareness make it the perfect choice for running on commodity hardware and in globally distributed cloud infrastructure. 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 - Transactional consistency across partitioned and distributed datasets - Parallel cross partition queries such as joins - 99.% 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 8.0.13-dmr, 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/8.0/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 8.0.13 (2018-10-23, Development Milestone) MySQL NDB Cluster 8.0.13 is a new development release of NDB 8.0, based on MySQL Server 8.0 and including features in version 8.0 of the NDB storage engine, as well as fixing recently discovered bugs in previous NDB Cluster releases. Obtaining NDB Cluster 8.0. NDB Cluster 8.0 source code and binaries can be obtained from https://dev.mysql.com/downloads/cluster/. For an overview of changes made in NDB Cluster 8.0, see What is New in NDB Cluster 8.0 (http://dev.mysql.com/doc/refman/8.0/mysql-cluster-what-is-new.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 8.0 through MySQL 8.0.13 (see Changes in MySQL 8.0.13 (2018-10-22) (http://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-13.html)). * Functionality Added or Changed * Bugs Fixed Functionality Added or Changed * Important Change; NDB Disk Data: The following changes are made in the display of information about Disk Data files in the INFORMATION_SCHEMA.FILES table: + Tablespaces and log file groups are no longer represented in the FILES table. (These constructs are not actually files.) + Each data file is now represented by a single row in the FILES table. Each undo log file is also now represented in this table by one row only. (Previously, a row was displayed for each copy of each of these files on each data node.) + For rows corresponding to data files or undo log files, node ID and undo log buffer information is no longer displayed in the EXTRA column of the FILES table. * Important Change; NDB Client Programs: Removed the deprecated --ndb option for perror. Use ndb_perror to obtain error message information from NDB error codes instead. (Bug #81705, Bug #23523957) References: See also: Bug #81704, Bug #23523926. * Important Change: Beginning with this release, MySQL NDB Cluster is being developed in parallel with the standard MySQL 8.0 server under a new unified release model with the following features: + NDB 8.0 is developed in, built from, and released with the MySQL 8.0 source code tree. + The numbering scheme for NDB Cluster 8.0 releases follows the scheme for MySQL 8.0, starting with the current MySQL release (8.0.13). + Building the source with NDB support appends -cluster to the version string returned by mysql -V, as shown here: shell≫ mysql -V mysql Ver 8.0.13-cluster for Linux on x86_64 (Source distribution) NDB binaries continue to display both the MySQL Server version and the NDB engine version, like this: shell> ndb_mgm -V MySQL distrib mysql-8.0.13 ndb-8.0.13-dmr, for Linux (x86_64) In MySQL Cluster NDB 8.0, these two version numbers are always the same. To build the MySQL 8.0.13 (or later) source w
MySQL Cluster 7.5.12 has been released
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.12, 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.12 (5.7.24-ndb-7.5.12) (2018-10-23,
General Availability)
MySQL NDB Cluster 7.5.12 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.24 (see Changes in MySQL 5.7.24 (2018-10-22,
General Availability)
(http://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-24.html)).
Bugs Fixed
* Packaging: Expected NDB header files were in the devel
RPM package instead of libndbclient-devel. (Bug #84580,
Bug #26448330)
* MySQL NDB ClusterJ: When a table containing a BLOB
(http://dev.mysql.com/doc/refman/5.7/en/blob.html) or a
TEXT (http://dev.mysql.com/doc/refman/5.7/en/blob.html)
field was being queried with ClusterJ for a record that
did not exist, an exception ("The method is not valid in
current blob state") was thrown. (Bug #28536926)
* MySQL NDB ClusterJ: A NullPointerException was thrown
when a full table scan was performed with ClusterJ on
tables containing either a BLOB or a TEXT field. It was
because the proper object initializations were omitted,
and they have now been added by this fix. (Bug #28199372,
Bug #91242)
* When the SUMA kernel block receives a SUB_STOP_REQ
signal, it executes the signal then replies with
SUB_STOP_CONF. (After this response is relayed back to
the API, the API is open to send more SUB_STOP_REQ
signals.) After sending the SUB_STOP_CONF, SUMA drops the
subscription if no subscribers are present, which
involves sending multiple DROP_TRIG_IMPL_REQ messages to
DBTUP. LocalProxy can handle up to 21 of these requests
in parallel; any more than this are queued in the Short
Time Queue. When execution of a DROP_TRIG_IMPL_REQ was
delayed, there was a chance for the queue to become
overloaded, leading to a data node shutdown with Error in
short time queue.
This issue is fixed by delaying the execution of the
SUB_STOP_REQ signal if DBTUP is already handling
DROP_TRIG_IMPL_REQ signals at full capacity, rather than
queueing up the DROP_TRIG_IMPL_REQ signals.
(Bug#26574003)
* Having a large number of deferred triggers could
sometimes lead to job buffer exhaustion. This could occur
due to the fact that a single trigger can execute many
operations---for example, a foreign key parent trigger
may perform operations on multiple matching child table
rows---and that a row operation on a base table can
execute multiple triggers. In such cases, row operations
are executed in batches. When execution of many triggers
was deferred---meaning that all deferred triggers are
executed at pre-commit---the resulting concurrent
execution of a great many trigger operations could cause
the data node job buffer or send buffer to be exhausted,
leading to failure of the node.
This issue is fixed by limiting the number of concurrent
trigger oper
MySQL Cluster 7.4.21 has been released
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.21, 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/ Enjoy ! Changes in MySQL NDB Cluster 7.4.21 (5.6.41-ndb-7.4.21) (2018-07-27, General Availability) MySQL NDB Cluster 7.4.21 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 http://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 (http://dev.mysql.com/doc/refman/5.6/en/mysql-cluster-what-is <http://dev.mysql.com/doc/refman/5.6/en/mysql-cluster-what-is-new-7-4.html>-new-7-4.html <http://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.41 (see Changes in MySQL 5.6.41 (Not yet released, General Availability) (http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-41.html)). Bugs Fixed * NDB Cluster APIs: When Ndb::dropEventOperation() tried to clean up a pending event, it failed to clear a pointer to the list of GCI operations being deleted and discarded (Gci_ops object), so that this pointer referred to a deleted object. GCI operations arriving after this could then be inserted as part of the next such list belonging to the now-deleted object, leading to memory corruption and other issues. (Bug #90011, Bug #27675005) * NDB attempted to drop subscriptions which had already been dropped, leading to a data node shutdown with Error 2341. (Bug #27622643) * An NDB online backup consists of data, which is fuzzy, and a redo and undo log. To restore to a consistent state it is necessary to ensure that the log contains all of the changes spanning the capture of the fuzzy data portion and beyond to a consistent snapshot point. This is achieved by waiting for a GCI boundary to be passed after the capture of data is complete, but before stopping change logging and recording the stop GCI in the backup's metadata. At restore time, the log is replayed up to the stop GCI, restoring the system to the state it had at the consistent stop GCI. A problem arose when, under load, it was possible to select a GCI boundary which occurred too early and did not span all the data captured. This could lead to inconsistencies when restoring the backup; these could be be noticed as broken constraints or corrupted BLOB entries. Now the stop GCI is chosen is so that it spans the entire duration of the fuzzy data capture process, so that the backup log always contains all data within a given stop GCI. (Bug #27497461) References: See also: Bug #27566346. On Behalf of MySQL Release Engineering team, Surabhi Bhat
MySQL Cluster 7.2.34 has been released
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 and Memcached) MySQL Cluster 7.2.34, 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.2/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.2.34 (5.5.61-ndb-7.2.34) (2018-07-27, General Availability) MySQL NDB Cluster 7.2.34 is a new release of NDB Cluster, incorporating new features in the NDB storage engine, and fixing recently discovered bugs in previous MySQL NDB Cluster 7.2 development releases. Obtaining MySQL NDB Cluster 7.2. MySQL NDB Cluster 7.2 source code and binaries can be obtained from http://dev.mysql.com/downloads/cluster/. 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.5 through MySQL 5.5.61 (see Changes in MySQL 5.5.61 (2018-07-27, General availability) (http://dev.mysql.com/doc/relnotes/mysql/5.5/en/news-5-5-61.html)). Bugs Fixed * NDB attempted to drop subscriptions which had already been dropped, leading to a data node shutdown with Error 2341. (Bug #27622643) -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Cluster 7.5.11 has been released
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.11, 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.11 (5.7.23-ndb-7.5.11) (2018-07-27, General Availability) MySQL NDB Cluster 7.5.11 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.23 (see Changes in MySQL 5.7.23 (2018-07-27, General Availability) (http://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-23.html)). Bugs Fixed * ndbinfo Information Database: It was possible following a restart for (sometimes incomplete) fallback data to be used in populating the ndbinfo.processes (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndbinfo-processes.html) table, which could lead to rows in this table with empty process_name values. Such fallback data is no longer used for this purpose. (Bug #27985339) * MySQL NDB ClusterJ: ClusterJ could not be built from source using JDK 9. (Bug #27977985) * NDB attempted to drop subscriptions which had already been dropped, leading to a data node shutdown with Error 2341. (Bug #27622643) * An NDB (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster.html) online backup consists of data, which is fuzzy, and a redo and undo log. To restore to a consistent state it is necessary to ensure that the log contains all of the changes spanning the capture of the fuzzy data portion and beyond to a consistent snapshot point. This is achieved by waiting for a GCI boundary to be passed after the capture of data is complete, but before stopping change logging and recording the stop GCI in the backup's metadata. At restore time, the log is replayed up to the stop GCI, restoring the system to the state it had at the consistent stop GCI. A problem arose when, under load, it was possible to select a GCI boundary which occurred too early and did not span all the data captured. This could lead to inconsistencies when restoring the backup; these could be be noticed as broken constraints or corrupted BLOB (http://dev.mysql.com/doc/refman/5.7/en/blob.html) entries. Now the stop GCI is chosen is so that it spans the entire duration of the fuzzy data capture process, so that the backup log always contains all data within a given stop GCI. (Bug #27497461) References: See also: Bug #27566346. * For NDB tables, when a foreign key was added or dropped as a part of a DDL statement, the foreign key metatdata for all parent tables referenced should be reloaded in the handler on all SQL nodes connected to the cluster, but this was done only on the mysqld on which the statement was executed. Due to this, any subsequent queries relying on foreign key metadata from the corresponding parent tables could return inconsistent results. (Bug #27439587) References: See also: Bug #82989, Bug #24666177. * The internal function Bitmask
MySQL Cluster 7.6.6 GA has been released
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-Paritioning (Sharding) - Read & write scalability - Transactional consistency across partitioned and distributed datasets - Parallel cross partition queries such as joins - Active-Active/Multi-Master geographic replication - 99.% High Availability with on-line maintenance and no single point of failure - NoSQL and SQL APIs (including C++, Java, http, Memcached and JavaScript/Node.js) MySQL Cluster 7.6.6 GA, 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.6 (5.7.22-ndb-7.6.6) (2018-05-31, General Availability) MySQL NDB Cluster 7.6.6 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 http://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.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)). Functionality Added or Changed * When performing an NDB backup, the ndbinfo.logbuffers table now displays information regarding buffer usage by the backup process on each data node. This is implemented as rows reflecting two new log types in addition to REDO and DD-UNDO. One of these rows has the log type BACKUP-DATA, which shows the amount of data buffer used during backup to copy fragments to backup files. The other row has the log type BACKUP-LOG, which displays the amount of log buffer used during the backup to record changes made after the backup has started. One each of these log_type rows is shown in the logbuffers table for each data node in the cluster. Rows having these two log types are present in the table only while an NDB backup is currently in progress. (Bug #25822988) * Added the --logbuffer-size option for ndbd and ndbmtd, for use in debugging with a large number of log messages. This controls the size of the data node log buffer; the default (32K) is intended for normal operations. (Bug #89679, Bug #27550943) * The previously experimental shared memory (SHM) transporter is now supported in production. SHM works by transporting signals through writing them into memory, rather than on a socket. NDB already attempts to use SHM automatically between data nodes and API nodes sharing the same host. To enable explicit shared memory connections, set the UseShm SHM configuration parameter to true. When explicitly defining shared memory as the connection method, it is also necessary to identify the nodes at either end of the connection (NodeId1 and NodeId2 parameters), and to provide a shared memory key (ShmKey). In addition, to improve performance, it is also possible to set a spin time (ShmSpinTime) for the SHM transporter. Configuration of SHM is otherwise similar to that of the TCP transporter. NDB Cluster Shared-Memory Connections (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-shm-definition.html) , provides additional information. * The SPJ kernel block now takes into account when it is evaluating a join request in which at least some of the tables are used in inner joins. This means that SPJ can eliminate requests for rows or ranges as soon as it becomes known that a preceding request did not return any results for a parent row. This saves both the data nodes and the SPJ block from having to handle requests and result rows which never take part in a result row from an inner join.
MySQL Cluster Manager 1.4.6 has been released
Dear MySQL Users, MySQL Cluster Manager 1.4.6 can be downloaded from the My Oracle Support (MOS) website. It will also be available on Oracle Software Delivery Cloud at http://edelivery.oracle.com with the next monthly update MySQL Cluster Manager is an optional component of the MySQL Cluster Carrier Grade Edition, providing a command-line interface that automates common management tasks, including the following online operations: - Configuring and starting MySQL Cluster - Upgrades - Adding and removing cluster nodes - Adding and removing site hosts - Configuration changes - Backup and restore MySQL Cluster Manager is a commercial extension to the MySQL family of products. More details can be found at http://www.mysql.com/products/cluster/mcm/. A brief summary of changes in MySQL Cluster Manager version 1.4.6 is listed below: Changes in MySQL Cluster Manager 1.4.6 (2018-05-09) * Functionality Added or Changed * Bugs Fixed Functionality Added or Changed * Agent: The list backups command has been extended with a new --agent option for listing agent backups created with the backup agents command. See the option description for details. (Bug #27168819, Bug #27850905) Bugs Fixed * Agent: The collect logs command failed to include logs that had been rotated with the rotate log command. (Bug #27918231) * Agent: A list backups command failed with an Error: 1159 (timeout reading communication packets) from one of the mcmd agents when it had a huge number of backups to list. With this fix, mcmd has been optimized to enumerate a larger number of backups. (Bug #27868499) * Agent: The mcmd agent quit unexpectedly if the cluster's global configuration file (config.ini usually) contained a [system] section. It was because in MySQL Cluster Manager, the handling for the [system] section was missing, which has now been added by this fix. The addition also allows mcmd to set the name attribute in the [system] section, which is required for MySQL Enterprise Monitor 4.0 to monitor the cluster. (Bug #27638138, Bug #27519205) * Agent: The collect logs command hung if a host was referenced earlier with the localhost IP address 127.0.0.1 in the create site or create cluster command. (Bug #27551932) * Agent: The create cluster command was successful even if the format of an IP address submitted with it as a hostname was inconsistent with the format used earlier with the add hosts command (for example, a host was added to a site as 127.0.0.1, and then added to a cluster as 127.0.01). A subsequent attempt to start the cluster failed. This fix added consistency check for the host names, so that inconsistent IP addresses are now rejected. (Bug #27551776) * Agent: When a maintenance restart occurred for a cluster node while mcmd was shutting down, the node remained in the starting stage indefinitely. With this fix, a node restart will not be attempted when mcmd is shutting down. (Bug #27513481) * Agent: An Internal error occurred when mcmd tried to set the MySQL Server system variable audit_log_read_buffer_size with a set command. It was because of the wrong data type used internally for the variable, which has now been fixed. (Bug #27413635) * Agent: mcmd quit unexpectedly sometimes when running a restore cluster command. It was due to a race condition in which mcmd started executing the restore before the required ndbapi node was ready for the task. This fix added checks to eliminate the race condition. (Bug #27342271) On behalf of MySQL Release Engineering Team, Surabhi Bhat
MySQL Cluster 7.6.5-dmr has been released
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.5-dmr, 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.5 (5.7.20-ndb-7.6.5) (2018-04-20, Development Milestone 5) MySQL NDB Cluster 7.6.5 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 http://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.20 (see Changes in MySQL 5.7.20 (2017-10-16, General Availability) (http://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-20.html)). Bugs Fixed * NDB Client Programs: On Unix platforms, the Auto-Installer failed to stop the cluster when ndb_mgmd was installed in a directory other than the default. (Bug #89624, Bug #27531186) * NDB Client Programs: The Auto-Installer did not provide a mechanism for setting the ServerPort parameter. (Bug #89623, Bug #27539823) * Writing of LCP control files was not always done correctly, which in some cases could lead to an unplanned shutdown of the cluster. This fix adds the requirement that upgrades from NDB 7.6.4 (or earlier) to this release (or a later one) include initial node restarts. (Bug #26640486) On Behalf of the MySQL/Oracle Release Engineering Team, Hery Ramilison -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Cluster 7.4.20 has been released
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.20, 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/ Enjoy ! == Changes in MySQL NDB Cluster 7.4.20 (5.6.40-ndb-7.4.20) (2018-04-20, General Availability) MySQL NDB Cluster 7.4.20 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 http://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 (http://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.40 (see Changes in MySQL 5.6.40 (2018-04-19, General Availability) (http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-40.html)). Bugs Fixed * NDB Cluster APIs: The maximum time to wait which can be specified when calling either of the NDB API methods Ndb::pollEvents() or pollEvents2() was miscalculated such that the method could wait up to 9 ms too long before returning to the client. (Bug #88924, Bug #27266086) * 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 #2908, Bug #25128512) References: See also: Bug #20112700. On Behalf of Oracle/MySQL Release Engineering Team, Daniel Horecki -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Cluster 7.5.10 has been released
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) *
MySQL Cluster 7.3.21 has been released
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.3.21, 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.3/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.3.21 (5.6.39-ndb-7.3.21) (2018-04-20, General Availability) MySQL NDB Cluster 7.3.21 is a new release of NDB Cluster, based on MySQL Server 5.6 and including features from version 7.3 of the NDB storage engine, as well as fixing a number of recently discovered bugs in previous NDB Cluster releases. Obtaining MySQL NDB Cluster 7.3. MySQL NDB Cluster 7.3 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.3, see What is New in NDB Cluster 7.3( http://dev.mysql.com/doc/refman/5.6/en/mysql-cluster-what-is-new-7-3.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.40 (see Changes in MySQL 5.6.40 (2018-04-19, General Availability)( http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-40.html )). Bugs Fixed * NDB Cluster APIs: Incorrect results, usually an empty result set, were returned when setBound() 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), and is fixed by rewriting the problematic internal logic in the old implementation. (Bug #89468, Bug #27461752) * Queries using very large lists with IN were not handled correctly, which could lead to data node failures. (Bug #27397802) * ndb_restore --print_data --hex did not print trailing 0s of LONGVARBINARY values. (Bug #65560, Bug #14198580) On Behalf of Oracle/MySQL Release Engineering Team Prashant Tekriwal
MySQL Cluster 7.6.4-dmr has been released
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.4-dmr, 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.4 (5.7.20-ndb-7.6.4) (2018-01-31, Development Milestone 4) MySQL NDB Cluster 7.6.4 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 http://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.20 (see Changes in MySQL 5.7.20 (2017-10-16, General Availability) (http://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-20.html)). * Functionality Added or Changed * Bugs Fixed Functionality Added or Changed * Incompatible Change; NDB Disk Data: Due to changes in disk file formats, it is necessary to perform an --initial restart of each data node when upgrading to or downgrading from this release. * Important Change; NDB Disk Data: NDB Cluster has improved node restart times and overall performance with larger data sets by implementing partial local checkpoints. Prior to this release, an LCP always made a copy of the entire database. NDB now supports LCPs that write individual records, so it is no longer strictly necessary for an LCP to write the entire database. Since, at recovery, it remains necessary to restore the database fully, the strategy is to save one fourth of all records at each LCP, as well as to write the records that have changed since the last LCP. Two data node configuration parameters relating to this change are introduced in this release: EnablePartialLcp (default true, or enabled) enables partial LCPs. When partial LCPs are enabled, RecoveryWork controls the percentage of space given over to LCPs; it increases with the amount of work which must be performed on LCPs during restarts as opposed to that performed during normal operations. Raising this value causes LCPs during normal operations to require writing fewer records and so decreases the usual workload. Raising this value also means that restarts can take longer. Important Upgrading disk data tables to NDB 7.6.4 or downgrading them from this release requires an initial restart of each data node. An initial node restart still requires a complete LCP; a partial LCP is not used for this purpose. This release also deprecates the data node configuration parameters BackupDataBufferSize, BackupWriteSize, and BackupMaxWriteSize; these are now subject to removal in a future NDB Cluster release. * Important Change: Added the ndb_perror utility for obtaining information about NDB Cluster error codes. This tool replaces perror --ndb; the --ndb option for perror is now deprecated and raises a warning when used; the option is subject to removal in a future NDB release. See ndb_perror --- Obtain NDB error message information (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-programs-ndb-perror.html), for more information. (Bug #81703, Bug #81704, Bug #23523869, Bug #23523926) References: See also: Bug #26966826, Bug #88086. * NDB Client Programs: NDB Cluster Auto-Installer node configuration parameters as supported in the UI and accompanying documentation were in some cases hard c
MySQL Cluster 7.4.18 has been released
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.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.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/ Enjoy ! Changes in MySQL NDB Cluster 7.4.18 (5.6.39-ndb-7.4.18) (2018-01-17, General Availability) MySQL NDB Cluster 7.4.18 was replaced following release by NDB 7.4.19. Users of NDB 7.4.17 and previous NDB 7.4 releases should upgrade directly to MySQL NDB Cluster 7.4.19 or later. For changes that originally appeared in NDB 7.4.18, see Section Section, "Changes in MySQL NDB Cluster 7.4.19 (5.6.39-ndb-7.4.19) (2018-01-23, General Availability)." -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Cluster 7.4.19 has been released
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.19, 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/ Enjoy ! Changes in MySQL NDB Cluster 7.4.19 (5.6.39-ndb-7.4.19) (2018-01-23, General Availability) MySQL NDB Cluster 7.4.19 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. NDB 7.4.19 replaces the NDB 7.4.18 release, and is the successor to NDB 7.4.17. Users of NDB 7.4.17 and previous NDB 7.4 releases should upgrade directly to MySQL NDB Cluster 7.4.19 or newer. Obtaining MySQL NDB Cluster 7.4. MySQL NDB Cluster 7.4 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.4, see What is New in NDB Cluster 7.4 (http://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 (including the NDB 7.4.18 release which this release replaces), as well as all bug fixes and feature changes which were added in mainline MySQL 5.6 through MySQL 5.6.39 (see Changes in MySQL 5.6.39 (2018-01-15, General Availability) (http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-39.html)). Bugs Fixed * NDB Replication: On an SQL node not being used for a replication channel with sql_log_bin=0 it was possible after creating and populating an NDB table for a table map event to be written to the binary log for the created table with no corresponding row events. This led to problems when this log was later used by a slave cluster replicating from the mysqld where this table was created. Fixed this by adding support for maintaining a cumulative any_value bitmap for global checkpoint event operations that represents bits set consistently for all rows of a specific table in a given epoch, and by adding a check to determine whether all operations (rows) for a specific table are all marked as NOLOGGING, to prevent the addition of this table to the Table_map held by the binlog injector. As part of this fix, the NDB API adds a new getNextEventOpInEpoch3() method which provides information about any AnyValue received by making it possible to retrieve the cumulative any_value bitmap. (Bug #26333981) * A query against the INFORMATION_SCHEMA.FILES table returned no results when it included an ORDER BY clause. (Bug #26877788) * During a restart, DBLQH loads redo log part metadata for each redo log part it manages, from one or more redo log files. Since each file has a limited capacity for metadata, the number of files which must be consulted depends on the size of the redo log part. These files are opened, read, and closed sequentially, but the closing of one file occurs concurrently with the opening of the next. In cases where closing of the file was slow, it was possible for more than 4 files per redo log part to be open concurrently; since these files were opened using the OM_WRITE_BUFFER option, more than 4 chunks of write buffer were allocated per part in such cases. The write buffer pool is not unlimited; if all redo log parts were in a similar state, the pool was exhausted, causing the data node to shut down. This issue is resolved by avoiding the use of OM_WRITE_BUFFER during metadata reload, so that any transient opening of more than 4 redo log files per log file part no longer l
MySQL Cluster 7.3.20 has been released
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.3.20, 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.3/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.3.20 (5.6.39-ndb-7.3.20) (2018-01-17, General Availability) MySQL NDB Cluster 7.3.20 is a new release of NDB Cluster, based on MySQL Server 5.6 and including features from version 7.3 of the NDB storage engine, as well as fixing a number of recently discovered bugs in previous NDB Cluster releases. Obtaining MySQL NDB Cluster 7.3. MySQL NDB Cluster 7.3 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.3, see What is New in NDB Cluster 7.3 (http://dev.mysql.com/doc/refman/5.6/en/mysql-cluster-what-is-new-7-3.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.39 (see Changes in MySQL 5.6.39 (Not yet released, General Availability) (http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-39.html)). Bugs Fixed * NDB Replication: On an SQL node not being used for a replication channel with sql_log_bin=0 it was possible after creating and populating an NDB table for a table map event to be written to the binary log for the created table with no corresponding row events. This led to problems when this log was later used by a slave cluster replicating from the mysqld where this table was created. Fixed this by adding support for maintaining a cumulative any_value bitmap for global checkpoint event operations that represents bits set consistently for all rows of a specific table in a given epoch, and by adding a check to determine whether all operations (rows) for a specific table are all marked as NOLOGGING, to prevent the addition of this table to the Table_map held by the binlog injector. As part of this fix, the NDB API adds a new getNextEventOpInEpoch3() method which provides information about any AnyValue received by making it possible to retrieve the cumulative any_value bitmap. (Bug #26333981) * A query against the INFORMATION_SCHEMA.FILES table returned no results when it included an ORDER BY clause. (Bug #26877788) * The NDBFS block's OM_SYNC flag is intended to make sure that all FSWRITEREQ signals used for a given file are synchronized, but was ignored by platforms that do not support O_SYNC, meaning that this feature did not behave properly on those platforms. Now the synchronization flag is used on those platforms that do not support O_SYNC. (Bug #76975, Bug #21049554) On Behalf of Oracle/MySQL Release Engineering Team Prashant Tekriwal
MySQL Cluster 7.5.9 has been released
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.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.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.9 (5.7.21-ndb-7.5.9) (2018-01-17, General Availability) MySQL NDB Cluster 7.5.9 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.21 (see Changes in MySQL 5.7.21 (Not yet released, General Availability) (http://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-21.html)). Bugs Fixed * NDB Replication: On an SQL node not being used for a replication channel with sql_log_bin=0 (http://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html#sysvar_sql_log_bin) it was possible after creating and populating an NDB table for a table map event to be written to the binary log for the created table with no corresponding row events. This led to problems when this log was later used by a slave cluster replicating from the mysqld where this table was created. Fixed this by adding support for maintaining a cumulative any_value bitmap for global checkpoint event operations that represents bits set consistently for all rows of a specific table in a given epoch, and by adding a check to determine whether all operations (rows) for a specific table are all marked as NOLOGGING, to prevent the addition of this table to the Table_map held by the binlog injector. As part of this fix, the NDB API adds a new getNextEventOpInEpoch3() (http://dev.mysql.com/doc/ndbapi/en/ndb-ndb-getnexteventopinepoch3.html) method which provides information about any AnyValue received by making it possible to retrieve the cumulative any_value bitmap. (Bug #26333981) * A query against the INFORMATION_SCHEMA.FILES (http://dev.mysql.com/doc/refman/5.7/en/files-table.html) table returned no results when it included an ORDER BY clause. (Bug #26877788) * During a restart, DBLQH loads redo log part metadata for each redo log part it manages, from one or more redo log files. Since each file has a limited capacity for metadata, the number of files which must be consulted depends on the size of the redo log part. These files are opened, read, and closed sequentially, but the closing of one file occurs concurrently with the opening of the next. In cases where closing of the file was slow, it was possible for more than 4 files per redo log part to be open concurrently; since these files were opened using the OM_WRITE_BUFFER option, more than 4 chunks of write buffer were allocated per part in such cases. The write buffer pool is not unlimited; if all redo log parts were in a similar state, the pool was exhausted, causing the data node to shut down. This issue is resolved by avoiding the use of OM_WRITE_BUFFER during metadata reload, so that any transient opening of more than 4 redo log files per log file part no longer leads to failure of the
MySQL Cluster 7.3.19 has been released
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.3.19, 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.3/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.3.19 (5.6.38-ndb-7.3.19) (2017-10-18, General Availability) MySQL NDB Cluster 7.3.19 is a new release of NDB Cluster, based on MySQL Server 5.6 and including features from version 7.3 of the NDB storage engine, as well as fixing a number of recently discovered bugs in previous NDB Cluster releases. Obtaining MySQL NDB Cluster 7.3. MySQL NDB Cluster 7.3 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.3, see What is New in NDB Cluster 7.3 (http://dev.mysql.com/doc/refman/5.6/en/mysql-cluster-what-is-new-7-3.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.38 (see Changes in MySQL 5.6.38 (Not yet released, General Availability) (http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-38.html)). Bugs Fixed * Added DUMP code 7027 to facilitate testing of issues relating to local checkpoints. For more information, see DUMP 7027 (http://dev.mysql.com/doc/ndb-internals/en/ndb-internals-dump-command-7027.html). (Bug #26661468) * A previous fix intended to improve logging of node failure handling in the transaction coordinator included logging of transactions that could occur in normal operation, which made the resulting logs needlessly verbose. Such normal transactions are no longer written to the log in such cases. (Bug #26568782) References: This issue is a regression of: Bug #26364729. * Some DUMP codes used for the LGMAN kernel block were incorrectly assigned numbers in the range used for codes belonging to DBTUX. These have now been assigned symbolic constants and numbers in the proper range (10001, 10002, and 10003). (Bug #26365433) * Node failure handling in the DBTC kernel block consists of a number of tasks which execute concurrently, and all of which must complete before TC node failure handling is complete. This fix extends logging coverage to record when each task completes, and which tasks remain, includes the following improvements: + Handling interactions between GCP and node failure handling interactions, in which TC takeover causes GCP participant stall at the master TC to allow it to extend the current GCI with any transactions that were taken over; the stall can begin and end in different GCP protocol states. Logging coverage is extended to cover all scenarios. Debug logging is now more consistent and understandable to users. + Logging done by the QMGR block as it monitors duration of node failure handling duration is done more frequently. A warning log is now generated every 30 seconds (instead of 1 minute), and this now includes DBDIH block debug information (formerly this was written separately, and less often). + To reduce space used, DBTC instance number: is shortened to DBTC number:. + A new error code is added to assist testing. (Bug #26364729) * A potential hundredfold signal fan-out when sending a START_FRAG_REQ signal could lead to a node failure due to a job buffer full error in start phase 5 while trying to perform a local checkpoint during a restart. (Bug #86675, Bug #26263397) References: See also: Bug #26288247, Bug #26279522. On Behalf of Oracle/MySQL Release Engineering Prashant Tekriwal
MySQL Cluster 7.4.17 has been released
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.17, 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/ Enjoy ! Changes in MySQL NDB Cluster 7.4.17 (5.6.38-ndb-7.4.17) (2017-10-18, General Availability) MySQL NDB Cluster 7.4.17 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 http://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 (http://dev.mysql.com/doc/refman/5.6/en/mysql-cluster-what-is <http://dev.mysql.com/doc/refman/5.6/en/mysql-cluster-what-is-new-7-4.html>-new-7-4.html <http://dev.mysql.com/doc/refman/5.6/en/mysql-cluster-what-is-new-7-4.html>). This release also incorporates all bugfixes and changes made in previous NDB Cluster releases, as well as all bugfixes and feature changes which were added in mainline MySQL 5.6 through MySQL 5.6.38 (see Changes in MySQL 5.6.38 (2017-10-16, General Availability) (http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-38 <http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-38.html>.html <http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-38.html>). Bugs Fixed * Added DUMP code 7027 to facilitate testing of issues relating to local checkpoints. For more information, see DUMP 7027 (http://dev.mysql.com/doc/ndb-internals/en/ndb-internals <http://dev.mysql.com/doc/ndb-internals/en/ndb-internals-dump-command-7027.html>-dump-command-7027.html <http://dev.mysql.com/doc/ndb-internals/en/ndb-internals-dump-command-7027.html>). (Bug #26661468) * A previous fix intended to improve logging of node failure handling in the transaction coordinator included logging of transactions that could occur in normal operation, which made the resulting logs needlessly verbose. Such normal transactions are no longer written to the log in such cases. (Bug #26568782) References: This issue is a regression of: Bug #26364729. * Some DUMP codes used for the LGMAN kernel block were incorrectly assigned numbers in the range used for codes belonging to DBTUX. These have now been assigned symbolic constants and numbers in the proper range (10001, 10002, and 10003). (Bug #26365433) * Node failure handling in the DBTC kernel block consists of a number of tasks which execute concurrently, and all of which must complete before TC node failure handling is complete. This fix extends logging coverage to record when each task completes, and which tasks remain, includes the following improvements: + Handling interactions between GCP and node failure handling interactions, in which TC takeover causes GCP participant stall at the master TC to allow it to extend the current GCI with any transactions that were taken over; the stall can begin and end in different GCP protocol states. Logging coverage is extended to cover all scenarios. Debug logging is now more consistent and understandable to users. + Logging done by the QMGR block as it monitors duration of node failure handling duration is done more frequently. A warning log is now generated every 30 seconds (instead of 1 minute), and this now includes DBDIH block debug information (formerly this was written separately, and less often). + To
MySQL Cluster 7.5.8 has been released
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.8, 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.8 (5.7.20-ndb-7.5.8) (2017-10-18, General Availability) MySQL NDB Cluster 7.5.8 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 bugfixes and changes made in previous NDB Cluster releases, as well as all bugfixes and feature changes which were added in mainline MySQL 5.7 through MySQL 5.7.20 (see Changes in MySQL 5.7.20 (Not yet released, General Availability) (http://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-20.html)). Bugs Fixed * Replication: With GTIDs generated for incident log events, MySQL error code 1590 (ER_SLAVE_INCIDENT) could not be skipped using the --slave-skip-errors=1590 startup option on a replication slave. (Bug #26266758) * Errors in parsing NDB_TABLE modifiers could cause memory leaks. (Bug #26724559) * Added DUMP code 7027 to facilitate testing of issues relating to local checkpoints. For more information, see DUMP 7027 (http://dev.mysql.com/doc/ndb-internals/en/ndb-internals-dump-command-7027.html). (Bug #26661468) * A previous fix intended to improve logging of node failure handling in the transaction coordinator included logging of transactions that could occur in normal operation, which made the resulting logs needlessly verbose. Such normal transactions are no longer written to the log in such cases. (Bug #26568782) References: This issue is a regression of: Bug #26364729. * Due to a configuration file error, CPU locking capability was not available on builds for Linux platforms. (Bug #26378589) * Some DUMP codes used for the LGMAN kernel block were incorrectly assigned numbers in the range used for codes belonging to DBTUX. These have now been assigned symbolic constants and numbers in the proper range (10001, 10002, and 10003). (Bug #26365433) * Node failure handling in the DBTC kernel block consists of a number of tasks which execute concurrently, and all of which must complete before TC node failure handling is complete. This fix extends logging coverage to record when each task completes, and which tasks remain, includes the following improvements: + Handling interactions between GCP and node failure handling interactions, in which TC takeover causes GCP participant stall at the master TC to allow it to extend the current GCI with any transactions that were taken over; the stall can begin and end in different GCP protocol states. Logging coverage is extended to cover all scenarios. Debug logging is now more consistent and understandable to users. + Logging done by the QMGR block as it monitors duration of node failure handling duration is done more frequently. A warning log is now generated every 30 seconds (instead of 1 minute), and this now includes DBDIH block debug information (formerly this was written separately, and less often). + To re
MySQL Cluster 7.5.7 has been released
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.7, 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.7 (5.7.19-ndb-7.5.7) (2017-07-19, General Availability) MySQL NDB Cluster 7.5.7 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 g://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 bugfixes and changes made in previous NDB Cluster releases, as well as all bugfixes and feature changes which were added in mainline MySQL 5.7 through MySQL 5.7.19 (see Changes in MySQL 5.7.19 (2017-07-17, General Availability) (http://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-19.html)). * Packaging Notes * Functionality Added or Changed * Bugs Fixed Packaging Notes * mysqladmin was added to Docker/Minimal packages because it is needed by InnoDB Cluster. (Bug #25998285) Functionality Added or Changed * Important Change; MySQL NDB ClusterJ: The ClusterJPA plugin for OpenJPA is no longer supported by NDB Cluster, and has been removed from the distribution. (Bug #23563810) * NDB Replication: Added the --ndb-log-update-minimal (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-options-variables.html#option_mysqld_ndb-log-update-minimal) option for logging by mysqld. This option causes only primary key values to be written in the before image, and only changed columns in the after image. (Bug #24438868) * NDB Cluster APIs; ndbinfo Information Database: Added two tables to the ndbinfo (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndbinfo.html) information database. The config_nodes (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndbinfo-config-nodes.html) table provides information about nodes that are configured as part of a given NDB Cluster, such as node ID and process type. The processes (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndbinfo-processes.html) table shows information about nodes currently connected to the cluster; this information includes the process name and system process ID, and service address. For each data node and SQL node, it also shows the process ID of the node's angel process. As part of the work done to implement the processes table, a new set_service_uri() (http://dev.mysql.com/doc/ndbapi/en/ndb-ndb-cluster-connection-set-service-uri.html) method has been added to the NDB API. For more information, see The ndbinfo config_nodes Table (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndbinfo-config-nodes.html), and The ndbinfo processes Table (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndbinfo-processes.html), as well as Ndb_cluster_connection::set_service_uri() (http://dev.mysql.com/doc/ndbapi/en/ndb-ndb-cluster-connection-set-service-uri.html). * NDB Cluster APIs: The system name of an NDB cluster is now visible in the mysql client as the value of the Ndb_system_name (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-options-variables.html#statvar_Ndb_system_name) status variable, and can also be obtained by NDB API application using the Ndb_cluster_connection::get_system_name() (http://dev.mysql.com/doc/ndbapi/en/ndb-ndb-clu
MySQL Cluster 7.3.18 has been released
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.3.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.3/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.3.18 (5.6.37-ndb-7.3.18) (2017-07-18, General Availability) MySQL NDB Cluster 7.3.18 is a new release of NDB Cluster, based on MySQL Server 5.6 and including features from version 7.3 of the NDB storage engine, as well as fixing a number of recently discovered bugs in previous NDB Cluster releases. Obtaining MySQL NDB Cluster 7.3. MySQL NDB Cluster 7.3 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.3, see What is New in NDB Cluster 7.3 (http://dev.mysql.com/doc/refman/5.6/en/mysql-cluster-what-is-new-7-3.html). This release also incorporates all bugfixes and changes made in previous NDB Cluster releases, as well as all bugfixes and feature changes which were added in mainline MySQL 5.6 through MySQL 5.6.37 (see Changes in MySQL 5.6.37 (2017-07-17, General Availability) (http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-37.html)). Functionality Added or Changed * Important Change; MySQL NDB ClusterJ: The ClusterJPA plugin for OpenJPA is no longer supported by NDB Cluster, and has been removed from the distribution. (Bug #23563810) Bugs Fixed * NDB Replication: Added a check to stop an NDB replication slave when configuration as a multi-threaded slave is detected (for example, if slave_parallel_workers is set to a nonzero value). (Bug #21074209) * Backup .log files contained log entries for one or more extra fragments, due to an issue with filtering out changes logged by other nodes in the same node group. This resulted in a larger .log file and thus use of more resources than necessary; it could also cause problems when restoring, since backups from different nodes could interfere with one another while the log was being applied. (Bug #25891014) * Error 240 is raised when there is a mismatch between foreign key trigger columns and the values supplied to them during trigger execution, but had no error message indicating the source of the problem. (Bug #23141739) References: See also: Bug #23068914, Bug #85857. * ALTER TABLE .. MAX_ROWS=0 can now be performed only by using a copying ALTER TABLE statement. Resetting MAX_ROWS to 0 can no longer be performed using ALGORITHM=INPLACE or the ONLINE keyword. (Bug #21960004) * When compiling the NDB kernel with gcc version 6.0.0 or later, it is now built using -flifetime-dse=1. (Bug #85381, Bug #25690926) On Behalf of the MySQL/Oracle Release Engineering Team, Kent Boortz & Hery Ramilison -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Cluster 7.4.16 has been released
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.16 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/ Enjoy ! == Changes in MySQL NDB Cluster 7.4.16 (5.6.37-ndb-7.4.16) (2017-07-18) MySQL NDB Cluster 7.4.16 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 http://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 (http://dev.mysql.com/doc/refman/5.6/en/mysql-cluster-what-is-new-7-4.html). This release also incorporates all bugfixes and changes made in previous NDB Cluster releases, as well as all bugfixes and feature changes which were added in mainline MySQL 5.6 through MySQL 5.6.37 (see Changes in MySQL 5.6.37 (Not yet released, General Availability) (http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-37.html)). * Functionality Added or Changed * Bugs Fixed Functionality Added or Changed * NDB Replication: Added the --ndb-log-update-minimal option for logging by mysqld. This option causes only primary key values to be written in the before image, and only changed columns in the after image. (Bug #24438868) * Added the --diff-default option for ndb_config. This option causes the program to print only those parameters having values that differ from their defaults. (Bug #85831, Bug #25844166) * Added the --query-all option to ndb_config. This option acts much like the --query option except that --query-all (short form: -a) dumps configuration information for all attributes at one time. (Bug #60095, Bug #11766869) Bugs Fixed * NDB Replication: Added a check to stop an NDB replication slave when configuration as a multi-threaded slave is detected (for example, if slave_parallel_workers is set to a nonzero value). (Bug #21074209) * NDB Cluster APIs: The implementation method NdbDictionary::NdbTableImpl::getColumn(), used from many places in the NDB API where a column is referenced by name, has been made more efficient. This method used a linear search of an array of columns to find the correct column object, which could be inefficient for tables with many columns, and was detected as a significant use of CPU in customer applications. (Ideally, users should perform name-to-column object mapping, and then use column IDs or objects in method calls, but in practice this is not always done.) A less costly hash index implementation, used previously for the name lookup, is reinstated for tables having relatively many columns. (A linear search continues to be used for tables having fewer columns, where the difference in performance is neglible.) (Bug #24829435) * MySQL NDB ClusterJ: The JTie and NDB JTie tests were skipped when the unit tests for ClusterJ were being run. (Bug #26088583) * Backup .log files contained log entries for one or more extra fragments, due to an issue with filtering out changes logged by other nodes in the same node group. This resulted in a larger .log file and thus use of more resources than necessary; it could also cause problems when restoring, since backups from different nodes could interfere with one another while the log was being applied. (Bug #25891014) * When ma
Re: MySQL Cluster Manager 1.4.3 has been released
Hi, Sree, I'm taking care of the release now. Docs should be up soon. Daniel On 10/07/2017 6:53 AM, Sreedhar S wrote: Dear MySQL Users, MySQL Cluster Manager 1.4.3 has been released and can be downloaded from the My Oracle Support (MOS) website. It will also be available on Oracle Software Delivery Cloud at http://edelivery.oracle.com with the next monthly update MySQL Cluster Manager is an optional component of the MySQL Cluster Carrier Grade Edition, providing a command-line interface that automates common management tasks, including the following online operations: - Configuring and starting MySQL Cluster - Upgrades - Adding and removing cluster nodes - Adding and removing site hosts - Configuration changes - Backup and restore MySQL Cluster Manager is a commercial extension to the MySQL family of products. More details can be found at http://www.mysql.com/products/cluster/mcm/ A brief summary of changes in MySQL Cluster Manager version 1.4.3 is listed below: Changes in MySQL Cluster Manager 1.4.3 (2017-07-10) This section documents all changes and bug fixes that have been applied in MySQL Cluster Manager 1.4.3 since the release of MySQL Cluster Manager version 1.4.2. Functionality Added or Changed * Agent: CPU usage during idle time for the mcmd agents has been significantly reduced. (Bug #26227736) * Agent: A new error code, Error 7030, has been created for failed ndb_mgmd commands and mysqld queries. (Bug #26160968) * Agent: Added support for the --skip-networking option for mysqld nodes, allowing mysqld nodes of a managed cluster to communicate with client applications using named pipes or shared memory on Windows platforms, and socket files on Unix-like platforms. Notice that, however, communication between mcmd agents and mcm clients using named pipes, shared memory, or socket files remain unsupported. (Bug #25992390, Bug #25974499) * Client: The start cluster --initial command now reinitializes the SQL nodes (if their data directories are empty) as well as the data nodes of an NDB Cluster. A new option, --skip-init, has been introduced, for specifying a comma-separated list of the SQL nodes for which reinitialization is to be skipped. (Bug #25856285, Bug #85713) * Client: Checksum verification has been added for all cluster reconfiguration plans created by the mcmd agents. Checksums for plans created locally are shared among all agents, and when the checksums do not match, the reconfiguration is aborted. This prevents agents from executing different plans. (Bug #23225839) * Files have been removed from the MySQL Cluster Manager + NDB Cluster bundled package, in order to reduce the package size significantly. (Bug #25916635) Bugs Fixed * Agent: When the list nextnodeid command was run against a cluster with the maximum number of nodes allowed, the mcmd agent quit unexpectedly. With this fix, the situation is properly handled. (Bug #26286531) * Agent: For a cluster with NoOfReplicas=1, trying to stop a data node with the stop process command would cause the agent to quit unexpectedly. (Bug #26259780) * Agent: When a data node was killed by an arbitrator in a situation of network partitioning, an mcmd failed to handle the exit report from the node and quit unexpectedly. It was due to a mishandling of the nodegroup information, which this fix corrects. (Bug #26192412) * Agent: A cluster could not be started if a relative path had been used for the --manager-directory option to set the location of the agent repository. (Bug #26172299) * Agent: When executing a user command, the mcmd agent could hang if the expected reply from another agent never arrived. This fix improves the timeout handling to avoid such hangs. (Bug #26168339) * Agent: While running the import config command, the mcmd agents that were present during the earlier dryrun for the import would become silent and then unavailable. This was due to some hostname resolution issues, which has been addressed by this fix. (Bug #26089906) * Agent: A collect log command sometimes failed at the middle with an ERROR 1003 Internal error: No clients connected. It was because the mcmd agent reset the copy completion marker prematurely; the behavior has been stopped by this fix. (Bug #26086958) * Agent: When the mcmd agents' clocks ran out of sync due to time drifts on virtual machines running Windows operations systems and then the clocks ran in sync again, communications among the agents failed. This fix prevents the problem by making the agents use a monotonic timer
MySQL Cluster 7.5.6 has been released
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.6, 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.6 (5.7.18-ndb-7.5.6) (2017-04-10, General Availability) MySQL NDB Cluster 7.5.6 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/. Repo packages for apt and yum can now be found at https://dev.mysql.com/downloads/repo/ For an overview of changes made in MySQL NDB Cluster 7.5, see What is New in MySQL NDB Cluster 7.5 (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-what-is-new.html). This release also incorporates all bugfixes and changes made in previous NDB Cluster releases, as well as all bugfixes and feature changes which were added in mainline MySQL 5.7 through MySQL 5.7.18 (see Changes in MySQL 5.7.18 (2017-04-10) (http://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-18.html)). Platform-Specific Notes * Ubuntu 14.04 and Ubuntu 16.04 are now supported. * The minimum required version of Solaris is now Solaris 11 update 3, due to a dependency on system runtime libraries. * On Solaris, MySQL is now built with Developer Studio 12.5 instead of gcc. The binaries require the Developer Studio C/C++ runtime libraries to be installed. See here for how to install only the libraries: https://docs.oracle.com/cd/E60778_01/html/E60743/gozsu.html Functionality Added or Changed * Packaging: Yum repo packages are added for EL5, EL6, EL7, and SLES12. Apt repo packages are added for Debian 7, Debian 8, Ubuntu 14.04, and Ubuntu 16.04 Bugs Fixed * Partitioning: The output of EXPLAIN PARTITIONS (http://dev.mysql.com/doc/refman/5.7/en/explain.html) displayed incorrect values in the partitions column when run on an explicitly partitioned NDB (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster.html) table having a large number of partitions. This was due to the fact that, when processing an EXPLAIN statement, mysqld calculates the partition ID for a hash value as (hash_value % number_of_partitions), which is correct only when the table is partitioned by HASH, since other partitioning types use different methods of mapping hash values to partition IDs. This fix replaces the partition ID calculation performed by mysqld with an internal NDB function which calculates the partition ID correctly, based on the table's partitioning type. (Bug #21068548) References: See also: Bug #25501895, Bug #14672885. * CPU usage of the data node's main thread by the DBDIH master block as the end of a local checkpoint could approach 100% in certain cases where the database had a very large number of fragment replicas. This is fixed by reducing the frequency and range of fragment queue checking during an LCP. (Bug #25443080) * The ndb_print_backup_file utility failed when attempting to read from a backup file when the backup included a table having more than 500 columns. (Bug #25302901) References: See also: Bug #25182956. * Multiple data node failures during a partial restart of the cluster could cause API nodes to fail. This was due to expansion of an internal object ID map by one thread, thus changing its location in memory, while another thread was still accessing the old loca
MySQL Cluster 7.2.28 has been released
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 and Memcached) MySQL Cluster 7.2.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.2/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.2.28 (5.5.55-ndb-7.2.28) (2017-04-10, General Availability) MySQL NDB Cluster 7.2.28 is a new release of NDB Cluster, incorporating new features in the NDB storage engine, and fixing recently discovered bugs in previous MySQL NDB Cluster 7.2 development releases. Obtaining MySQL NDB Cluster 7.2. MySQL NDB Cluster 7.2 source code and binaries can be obtained from http://dev.mysql.com/downloads/cluster/. This release also incorporates all bugfixes and changes made in previous NDB Cluster releases, as well as all bugfixes and feature changes which were added in mainline MySQL 5.5 through MySQL 5.5.55 (see Changes in MySQL 5.5.55 (2017-04-10, General availability) (http://dev.mysql.com/doc/relnotes/mysql/5.5/en/news-5-5-55.html)). Bugs Fixed * NDB Disk Data: Stale data from NDB Disk Data tables that had been dropped could potentially be included in backups due to the fact that disk scans were enabled for these. To prevent this possibility, disk scans are now disabled---as are other types of scans---when taking a backup. (Bug #84422, Bug #25353234) * NDB Disk Data: In some cases, setting dynamic in-memory columns of an NDB Disk Data table to NULL was not handled correctly. (Bug #79253, Bug #22195588) -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Cluster Manager 1.4.2 has been released
Dear MySQL Users, MySQL Cluster Manager 1.4.2 has been released and can be downloaded from the My Oracle Support (MOS) website. It will also be available on Oracle Software Delivery Cloud at http://edelivery.oracle.com with the next monthly update MySQL Cluster Manager is an optional component of the MySQL Cluster Carrier Grade Edition, providing a command-line interface that automates common management tasks, including the following online operations: - Configuring and starting MySQL Cluster - Upgrades - Adding and removing cluster nodes - Adding and removing site hosts - Configuration changes - Backup and restore MySQL Cluster Manager is a commercial extension to the MySQL family of products. More details can be found at http://www.mysql.com/products/cluster/mcm/ A brief summary of changes in MySQL Cluster Manager version 1.4.2 is listed below: Changes in MySQL Cluster Manager 1.4.2 (2017-03-07) This section documents all changes and bug fixes that have been applied in MySQL Cluster Manager 1.4.2 since the release of MySQL Cluster Manager version 1.4.1. Functionality Added or Changed * Agent: To allow easy detection of an incomplete agent backup, an empty file named INCOMPLETE is created in the folder in which the backup is created when the backup agents command begins, and is deleted after the backup is finished. The continuous existence of the file after the backup process is over indicates that the backup is incomplete. (Bug #25126866) * Agent: MySQL Cluster Manager can now recover automatically a failed mysqld node, as long as the data directory of the node is empty when recovery is attempted; if that is not the case, after cleaning up the data directory manually, users can now manually run the start process --initial to rebuild the mysqld node's data directory. (Bug #18415446) * Agent: A new command, update process, imports a process back into the control of mcmd after mcmd has lost track of the process' status due to different reasons (for example, it has been restarted manually outside of MySQL Cluster Manager). For more details, see the description of the command. * Agent: The show status command now reports progress when the new --progress or --progressbar options is used. Bugs Fixed * Agent: When a custom FileSystemPath value was used for a data node, the list backups and restore cluster commands failed, as the backup directory could not be found. (Bug #25549903) * Agent: In some situations, a certain mcmd agent took too long to process event messages that a synchronization timeout occurred among the agents. This was because the agent went into a mutex contention for file access, which this fix removes. (Bug #25462861) * Agent: The collect logs command reported success even if file transfers were incomplete. This fix adds checks for file transfer completion and reports any errors. (Bug #25436057) * Agent: An ndbmtd node sometimes (for example, at a rolling restart of the cluster) sent out a large amount of event messages, and it might take too long for an mcmd agent to process them that the agent lagged behind on its readiness for the next command, resulting in a synchronization timeout among the mcmd agents. This fix drastically reduced the amount of event messages sent by an ndbmtd node, thus reducing the chance of a synchronization timeout under the situation. (Bug #25358050) * Agent: A management node failure might trigger mcmd to quit unexpectedly on Windows platforms. (Bug #25336594) * Agent: Multiple errors thrown by the backup agents, rotate logs, and change log-level commands could potentially overwrite each other, causing a lost of error information. (Bug #25134452) * Agent: The collect logs command hung when TCP connections could not be established between the agent that initiated the command and the other agents. This fix makes the command timeout after the situation persists for more than 30s. Also, a new mcmd option, --copy-port, has been added, by which users can specify the TCP port number to be used for log copying. (Bug #25064313) * Agent: The .mcm file created by the import config --dryrun command sometimes have certain configuration settings missing from it. (Bug #24962848) * Agent: A restore cluster command would fail if MySQL Cluster Manager did not have write access to the BackupDataDir of each data node. The unnecessary requirement has now been removed. (Bug #24763936) * Agent: If a stop cluster or a stop process command had failed, a restart on some of the processes might fail
MySQL Cluster 7.5.5 has been released
Dear MySQL Users, MySQL Cluster 7.5.5 (GA) is a GA release for MySQL Cluster 7.5. 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.5, 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.5 (5.7.17-ndb-7.5.5) (2017-01-17) MySQL Cluster NDB 7.5.5 is a new release of MySQL Cluster NDB 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 MySQL Cluster releases. Obtaining MySQL Cluster NDB 7.5. MySQL Cluster NDB 7.5 source code and binaries can be obtained from http://dev.mysql.com/downloads/cluster/. For an overview of changes made in MySQL Cluster NDB 7.5, see What is New in MySQL NDB Cluster 7.5 (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-what-is-new.html). This release also incorporates all bugfixes and changes made in previous MySQL Cluster releases, as well as all bugfixes and feature changes which were added in mainline MySQL 5.7 through MySQL 5.7.17 (see Changes in MySQL 5.7.17 (2016-12-12) , General Availability) (http://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-17.html)). Bugs Fixed * Packaging: The RPM installer for the MySQL Cluster auto-installer package had a dependency on python2-crypt instead of python-crypt. (Bug #24924607) * Microsoft Windows: Installation failed when the Auto-Installer (ndb_setup.py) was run on a Windows host that used Swedish as the system language. This was due to system messages being issued using the cp1252 character set; when these messages contained characters that did not map directly to 7-bit ASCII (such as the ä character in Tjänsten ... startar), conversion to UTF-8---as expected by the Auto-Installer web client---failed. This fix has been tested only with Swedish as the system language, but should work for Windows systems set to other European languages that use the cp1252 character set. (Bug #83870, Bug #25111830) * No traces were written when ndbmtd received a signal in any thread other than the main thread, due to the fact that all signals were blocked for other threads. This issue is fixed by the removal of SIGBUS, SIGFPE, SIGILL, and SIGSEGV signals from the list of signals being blocked. (Bug #25103068) * The rand() function was used to produce a unique table ID and table version needed to identify a schema operation distributed between multiple SQL nodes, relying on the assumption that rand() would never produce the same numbers on two different instances of mysqld. It was later determined that this is not the case, and that in fact it is very likely for the same random numbers to be produced on all SQL nodes. This fix removes the usage of rand() for producing a unique table ID or version, and instead uses a sequence in combination with the node ID of the coordinator. This guarantees uniqueness until the counter for the sequence wraps, which should be sufficient for this purpose. The effects of this duplication could be observed as timeouts in the log (for example NDB create db: waiting max 119 sec for distributing) when restarting multiple mysqld processes simultaneously or nearly so, or when issuing the same CREATE DATABASE (http://dev.mysql.com/doc/refman/5.7/en/create-database.html) or DROP DATABASE (http://dev.mysql.com/doc/refman/5.7/en/drop-database.html) statement on multiple SQL nodes. (Bug #24926009) * The ndb_show_tables utility did not display type information for hash maps or fully replicated triggers. (Bug #24383742) * Long message buffer exhaustion when firing immediate triggers could result in row ID l
MySQL Cluster 7.2.27 has been released
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 and Memcached) MySQL Cluster 7.2.27, 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.2/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.2.27 (5.5.54-ndb-7.2.27) (2017-01-17) MySQL NDB Cluster 7.2.27 is a new release of NDB Cluster, incorporating new features in the NDB storage engine, and fixing recently discovered bugs in previous MySQL NDB Cluster 7.2 development releases. Obtaining MySQL NDB Cluster 7.2. MySQL NDB Cluster 7.2 source code and binaries can be obtained from http://dev.mysql.com/downloads/cluster/. This release also incorporates all bugfixes and changes made in previous NDB Cluster releases, as well as all bugfixes and feature changes which were added in mainline MySQL 5.5 through MySQL 5.5.54 (see Changes in MySQL 5.5.54 (2016-12-12, General availability) (http://dev.mysql.com/doc/relnotes/mysql/5.5/en/news-5-5-54.html)). Bugs Fixed * A number of potential buffer overflow issues were found and fixed in the NDB codebase. (Bug #25260091) References: See also: Bug #23152979. * ndb_restore did not restore tables having more than 341 columns correctly. This was due to the fact that the buffer used to hold table metadata read from .ctl files was of insufficient size, so that only part of the table descriptor could be read from it in such cases. This issue is fixed by increasing the size of the buffer used by ndb_restore for file reads. (Bug #25182956) On Behalf of MySQL Release Engineering Team, Gipson Pulla -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Cluster 7.3.15 has been released
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.3.15, 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.3/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 Cluster NDB 7.3.15 (5.6.34-ndb-7.3.15) (2016-10-18) MySQL Cluster NDB 7.3.15 is a new release of MySQL Cluster, based on MySQL Server 5.6 and including features from version 7.3 of the NDB storage engine, as well as fixing a number of recently discovered bugs in previous MySQL Cluster releases. Obtaining MySQL Cluster NDB 7.3. MySQL Cluster NDB 7.3 source code and binaries can be obtained from http://dev.mysql.com/downloads/cluster/. For an overview of changes made in MySQL Cluster NDB 7.3, see What is New in MySQL Cluster NDB 7.3 (http://dev.mysql.com/doc/refman/5.6/en/mysql-cluster-what-is-new-7-3.html). This release also incorporates all bugfixes and changes made in previous MySQL Cluster releases, as well as all bugfixes and feature changes which were added in mainline MySQL 5.6 through MySQL 5.6.34 (see Changes in MySQL 5.6.34 (2016-10-12, General Availability) (http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-34.html)). * Functionality Added or Changed * Bugs Fixed Functionality Added or Changed * ClusterJ: To help applications handle database errors better, a number of new features have been added to the ClusterJDatastoreException class: + A new method, getCode(), returns code from the NdbError object. + A new method, getMysqlCode(), returns mysql_code from the NdbError object. + A new subclass, ClusterJDatastoreException.Classification, gives users the ability to decode the result from getClassification(). The method Classification.toString() gives the name of the error classification as listed in NDB Error Classifications (http://dev.mysql.com/doc/ndbapi/en/ndb-error-classifications.html). (Bug #22353594) Bugs Fixed * Removed an invalid assertion to the effect that all cascading child scans are closed at the time API connection records are released following an abort of the main transaction. The assertion was invalid because closing of scans in such cases is by design asynchronous with respect to the main transaction, which means that subscans may well take some time to close after the main transaction is closed. (Bug #23709284) * A number of potential buffer overflow issues were found and fixed in the NDB codebase. (Bug #23152979) * When a data node has insufficient redo buffer during a system restart, it does not participate in the restart until after the other nodes have started. After this, it performs a takeover of its fragments from the nodes in its node group that have already started; during this time, the cluster is already running and user activity is possible, including DML and DDL operations. During a system restart, table creation is handled differently in the DIH kernel block than normally, as this creation actually consists of reloading table definition data from disk on the master node. Thus, DIH assumed that any table creation that occurred before all nodes had restarted must be related to the restart and thus always on the master node. However, during the takeover, table creation can occur on non-master nodes due to user activity; when this happened, the cluster underwent a forced shutdown. Now an extra check is made during system restarts to detect in such cases whether the executing node is the master node, and use that information to determine whether the table creation is part of the restart proper, or is taking place during a subsequent takeover.
MySQL Cluster 7.2.25 has been released
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 and Memcached) MySQL Cluster 7.2.25, 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.2/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 Cluster NDB 7.2.25 (5.5.50-ndb-7.2.25) (2016-07-18) MySQL Cluster NDB 7.2.25 is a new release of MySQL Cluster, incorporating new features in the NDB storage engine, and fixing recently discovered bugs in previous MySQL Cluster NDB 7.2 development releases. Obtaining MySQL Cluster NDB 7.2. MySQL Cluster NDB 7.2 source code and binaries can be obtained from http://dev.mysql.com/downloads/cluster/. This release also incorporates all bugfixes and changes made in previous MySQL Cluster releases, as well as all bugfixes and feature changes which were added in mainline MySQL 5.5 through MySQL 5.5.50 (see Changes in MySQL 5.5.50 (2016-06-02) (http://dev.mysql.com/doc/relnotes/mysql/5.5/en/news-5-5-50.html)). Bugs Fixed * Incompatible Change: When the data nodes are only partially connected to the API nodes, a node used for a pushdown join may get its request from a transaction coordinator on a different node, without (yet) being connected to the API node itself. In such cases, the NodeInfo object for the requesting API node contained no valid info about the software version of the API node, which caused the DBSPJ block to assume (incorrectly) when aborting to assume that the API node used NDB version 7.2.4 or earlier, requiring the use of a backward compatability mode to be used during query abort which sent a node failure error instead of the real error causing the abort. Now, whenever this situation occurs, it is assumed that, if the NDB software version is not yet available, the API node version is greater than 7.2.4. (Bug #23049170) On behalf of Oracle MySQL RE team Gipson Pulla -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Cluster 7.5.2 has been released (part 2/2)
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.2 DMR, 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 Cluster NDB 7.5.2 (5.7.12-ndb-7.5.2) (2016-06-01, Developer Milestone 3) MySQL Cluster NDB 7.5.2 is a new release of MySQL 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 MySQL Cluster releases. Obtaining MySQL Cluster NDB 7.5. MySQL Cluster NDB 7.5 source code and binaries can be obtained from http://dev.mysql.com/downloads/cluster/. For an overview of changes made in MySQL Cluster NDB 7.5, see What is New in MySQL Cluster NDB 7.5 (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-what-is -new.html <http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-what-is-new.html>). This release also incorporates all bugfixes and changes made in previous MySQL Cluster releases, as well as all bugfixes and feature changes which were added in mainline MySQL 5.7 through MySQL 5.7.12 (see Changes in MySQL 5.7.12 (2016-04-11) (http://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-12.h tml <http://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-12.html>)). Bugs Fixed * Performance: A performance problem was found in an internal polling method do_poll() where the polling client did not check whether it had itself been woken up before completing the poll. Subsequent analysis showed that it is sufficient that only some clients in the polling queue receive data. do_poll() can then signal these clients and give up its polling rights, even if the maximum specified wait time (10 ms) has not expired. This change allows do_poll() to continue polling until either the maximum specified wait time has expired, or the polling client itself has been woken up (by receiving what it was waiting for). This avoids unnecessary thread switches between client threads and thus reduces the associated overhead by as much as 10% in the API client, resulting in a significant performance improvement when client threads perform their own polling. (Bug #81229, Bug #23202735) * Incompatible Change: When the data nodes are only partially connected to the API nodes, a node used for a pushdown join may get its request from a transaction coordinator on a different node, without (yet) being connected to the API node itself. In such cases, the NodeInfo object for the requesting API node contained no valid info about the software version of the API node, which caused the DBSPJ block to assume (incorrectly) when aborting to assume that the API node used NDB version 7.2.4 or earlier, requiring the use of a backward compatability mode to be used during query abort which sent a node failure error instead of the real error causing the abort. Now, whenever this situation occurs, it is assumed that, if the NDB software version is not yet available, the API node version is greater than 7.2.4. (Bug #23049170) * Important Change: When started with the --initialize (http://dev.mysql.com/doc/refman/5.7/en/server-options.ht ml#option_mysqld_initialize <http://dev.mysql.com/doc/refman/5.7/en/server-options.html#option_mysqld_initialize>) option, mysqld no longer enables the NDBCLUSTER (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster.htm l <http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster.html>) storage engine plugin. This change was needed to prevent attempted initialization of system databases as distributed (rather than as specific to individual SQL nodes), which could result in a metadata lock deadlock. This fix also brings
MySQL Cluster 7.5.2 has been released (part 1/2)
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.2 DMR, 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 Cluster NDB 7.5.2 (5.7.12-ndb-7.5.2) (2016-06-01, Developer Milestone 3) MySQL Cluster NDB 7.5.2 is a new release of MySQL 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 MySQL Cluster releases. Obtaining MySQL Cluster NDB 7.5. MySQL Cluster NDB 7.5 source code and binaries can be obtained from http://dev.mysql.com/downloads/cluster/. For an overview of changes made in MySQL Cluster NDB 7.5, see What is New in MySQL Cluster NDB 7.5 (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-what-is -new.html <http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-what-is-new.html>). This release also incorporates all bugfixes and changes made in previous MySQL Cluster releases, as well as all bugfixes and feature changes which were added in mainline MySQL 5.7 through MySQL 5.7.12 (see Changes in MySQL 5.7.12 (2016-04-11) (http://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-12.h tml <http://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-12.html>)). Functionality Added or Changed * Performance: A deficiency in event buffer memory allocation was identified as inefficient and possibly leading to undesirable results. This could happen when additional memory was allocated from the operating system to buffer received event data even when memory had already been allocated but remained unused. This is fixed by allocating the event buffer memory directly from the page allocation memory manager (mmap()), where such functionality is offered by the operating system, allowing for direct control over the memory such that it is in fact returned to the system when released. This remimplementation avoids the tendencies of the existing one to approach worst-case memory usage, maintainence of data structures for a worst-case event buffer event count, and useless caching of free memory in unusable positions. This work should also help minimize the runtime costs of buffering events, minimize heap fragmentation, and avoid OS-specific problems due to excessive numbers of distinct memory mappings. In addition, the relationship between epochs and internal EventData objects is now preserved throughout the event lifecycle, reception to consumption, thus removing the need for iterating, and keeping in synch, two different lists representing the epochs and their EventData objects. As part of this work, better reporting on the relevant event buffer metrics is now provided in the cluster logs. References: See also: Bug #21651536, Bug #21660947, Bug #21661297, Bug #21673318, Bug #21689380, Bug #21809959. * ndb_restore now performs output logging for specific stages of its operation. (Bug #21097957) * An improvement in the hash index implementation used by MySQL Cluster data nodes means that partitions may now contain more than 16 GB of data for fixed columns, and the maximum partition size for fixed column data is now increased to 128 TB. The previous limitation originated with the DBACC block in the NDB (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster.htm l <http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster.html>) kernel using only 32-bit references to the fixed-size part of a row handled in the DBTUP block, even though 45-bit references were already in use elsewhere in the kernel outside the DBACC block; all such references in DBACC now use 45-bit pointers instead. As part of this work, error messages return
MySQL Cluster 7.2.24 has been released
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 and Memcached) MySQL Cluster 7.2.24, 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.2/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 Cluster NDB 7.2.24 (5.5.48-ndb-7.2.24) (2016-04-19) MySQL Cluster NDB 7.2.24 is a new release of MySQL Cluster, incorporating new features in the NDB storage engine, and fixing recently discovered bugs in previous MySQL Cluster NDB 7.2 development releases. Obtaining MySQL Cluster NDB 7.2. MySQL Cluster NDB 7.2 source code and binaries can be obtained from http://dev.mysql.com/downloads/cluster/. This release also incorporates all bugfixes and changes made in previous MySQL Cluster releases, as well as all bugfixes and feature changes which were added in mainline MySQL 5.5 through MySQL 5.5.48 (see Changes in MySQL 5.5.48 (2016-02-05) (http://dev.mysql.com/doc/relnotes/mysql/5.5/en/news-5-5-48.html)). Bugs Fixed * Restoration of metadata with ndb_restore -m occasionally failed with the error message Failed to create index... when creating a unique index. While diagnosing this problem, it was found that the internal error PREPARE_SEIZE_ERROR (a temporary error) was reported as an unknown error. Now in such cases, ndb_restore retries the creation of the unique index, and PREPARE_SEIZE_ERROR is reported as NDB Error 748 Busy during read of event table. (Bug #21178339) References: See also Bug #22989944.
MySQL Cluster 7.2.23 has been released
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 and Memcached) MySQL Cluster 7.2.23, 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.2/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 Cluster NDB 7.2.23 (5.5.47-ndb-7.2.23) (2016-01-19) MySQL Cluster NDB 7.2.23 is a new release of MySQL Cluster, incorporating new features in the NDB storage engine, and fixing recently discovered bugs in previous MySQL Cluster NDB 7.2 development releases. Obtaining MySQL Cluster NDB 7.2. MySQL Cluster NDB 7.2 source code and binaries can be obtained from http://dev.mysql.com/downloads/cluster/. This release also incorporates all bugfixes and changes made in previous MySQL Cluster releases, as well as all bugfixes and feature changes which were added in mainline MySQL 5.5 through MySQL 5.5.47 (see Changes in MySQL 5.5.47 (2015-12-07) (http://dev.mysql.com/doc/relnotes/mysql/5.5/en/news-5-5-47.html)). Bugs Fixed * In debug builds, a WAIT_EVENT while polling caused excessive logging to stdout. (Bug #22203672) * When executing a schema operation such as CREATE TABLE on a MySQL Cluster with multiple SQL nodes, it was possible for the SQL node on which the operation was performed to time out while waiting for an acknowledgement from the others. This could occur when different SQL nodes had different settings for --ndb-log-updated-only, --ndb-log-update-as-write, or other mysqld options effecting binary logging by NDB. This happened due to the fact that, in order to distribute schema changes between them, all SQL nodes subscribe to changes in the ndb_schema system table, and that all SQL nodes are made aware of each others subscriptions by subscribing to TE_SUBSCRIBE and TE_UNSUBSCRIBE events. The names of events to subscribe to are constructed from the table names, adding REPL$ or REPLF$ as a prefix. REPLF$ is used when full binary logging is specified for the table. The issue described previously arose because different values for the options mentioned could lead to different events being subscribed to by different SQL nodes, meaning that all SQL nodes were not necessarily aware of each other, so that the code that handled waiting for schema distribution to complete did not work as designed. To fix this issue, MySQL Cluster now treats the ndb_schema table as a special case and enforces full binary logging at all times for this table, independent of any settings for mysqld binary logging options. (Bug #22174287, Bug #79188) * Using ndb_mgm STOP -f to force a node shutdown even when it triggered a complete shutdown of the cluster, it was possible to lose data when a sufficient number of nodes were shut down, triggering a cluster shutodwn, and the timing was such that SUMA handovers had been made to nodes already in the process of shutting down. (Bug #17772138) * The internal NdbEventBuffer::set_total_buckets() method calculated the number of remaining buckets incorrectly. This caused any incomplete epoch to be prematurely completed when the SUB_START_CONF signal arrived out of order. Any events belonging to this epoch arriving later were then ignored, and so effectively lost, which resulted in schema changes not being distributed correctly among SQL nodes. (Bug #79635, Bug #22363510) * Schema events were appended to the binary log out of order relative to non-schema events. This was caused by the fact that the binlog injector did not properly handle the case where schema events and non-schema events were from different epochs. This fix modifies the handling of events from the two schema and non-schema event streams such that events are now always handled one epoch at a
MySQL Cluster 7.4.9 has been released
Dear MySQL Users, MySQL Cluster is the distributed, shared-nothing variant of MySQL. This storage engine provides: - In-memory persistent 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.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. 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/ Enjoy ! Changes in MySQL Cluster NDB 7.4.9 (5.6.28-ndb-7.4.9) (2016-01-18 ) MySQL Cluster NDB 7.4.9 is a new release of MySQL 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 MySQL Cluster releases. Obtaining MySQL Cluster NDB 7.4. MySQL Cluster NDB 7.4 source code and binaries can be obtained from http://dev.mysql.com/downloads/cluster/. For an overview of changes made in MySQL Cluster NDB 7.4, see MySQL Cluster Development in MySQL Cluster NDB 7.4 ( http://dev.mysql.com/doc/refman/5.6/en/mysql-cluster-development- 5-6-ndb-7-4.htm l). This release also incorporates all bugfixes and changes made in previous MySQL Cluster releases, as well as all bugfixes and feature changes which were added in mainline MySQL 5.6 through MySQL 5.6.28 (see Changes in MySQL 5.6.28 (2015-12-07) (http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-28.html)). Functionality Added or Changed * Important Change: Previously, the NDB scheduler always optimized for speed against throughput in a predetermined manner (this was hard coded); this balance can now be set using the SchedulerResponsiveness data node configuration parameter. This parameter accepts an integer in the range of 0-10 inclusive, with 5 as the default. Higher values provide better response times relative to throughput. Lower values provide increased throughput, but impose longer response times. (Bug #78531, Bug #21889312) * Added the tc_time_track_stats table to the ndbinfo information database. This table provides time-tracking information relating to transactions, key operations, and scan operations performed by NDB. (Bug #78533, Bug #21889652) * Cluster Replication: Normally, RESET SLAVE causes all entries to be deleted from the mysql.ndb_apply_status table. This release adds the ndb_clear_apply_status system variable, which makes it possible to override this behavior. This variable is ON by default; setting it to OFF keeps RESET SLAVE from purging the ndb_apply_status table. (Bug #12630403) Bugs Fixed * Important Change: Users can now set the number and length of connection timeouts allowed by most NDB programs with the --connect-retries and --connect-retry-delay command line options introduced for the programs in this release. For ndb_mgm, --connect-retries supersedes the existing --try-reconnect option. (Bug #57576, Bug #11764714) * When executing a schema operation such as CREATE TABLE on a MySQL Cluster with multiple SQL nodes, it was possible for the SQL node on which the operation was performed to time out while waiting for an acknowledgement from the others. This could occur when different SQL nodes had different settings for --ndb-log-updated-only, --ndb-log-update-as-write, or other mysqld options effecting binary logging by NDB. This happened due to the fact that, in order to distribute schema changes between them, all SQL nodes subscribe to changes in the ndb_schema system table, and that all SQL nodes are made aware of each others subscriptions by subscribing to TE_SUBSCRIBE and TE_UNSUBSCRIBE events. The names of events to subscribe to are constructed from the table names, adding REPL$ or REPLF$ as a prefix. REPLF$ is used when full binary logging is specified for the table. The issue described previously arose because different values for the options mentioned could lead to different events being subscribed to by different SQL nodes, meaning that all SQL nodes were not necessarily aware of each other, so that the code that handled waiting for schema distribution to complete did not work as desi
MySQL Cluster Manager 1.4.0 has been released
Hello all, MySQL Cluster Manager 1.4.0, has been released and can be downloaded from the My Oracle Support (MOS) website. It will also be available on Oracle Software Delivery Cloud at http://edelivery.oracle.com with the next monthly update MySQL Cluster Manager is an optional component of the MySQL Cluster Carrier Grade Edition, providing a command-line interface that automates common management tasks, including the following online operations: - Configuring and starting MySQL Cluster - Upgrades - Adding and removing cluster nodes - Adding and removing site hosts - Configuration changes - Backup and restore MySQL Cluster Manager is a commercial extension to the MySQL family of products. More details can be found at http://www.mysql.com/products/cluster/mcm/ A brief summary of changes in MySQL Cluster Manager version 1.4.0 is listed below: Changes in MySQL Cluster Manager 1.4.0 (2015-12-07) This section documents all changes and bug fixes that have been applied in MySQL Cluster Manager 1.4.0 since the release of MySQL Cluster Manager version 1.3.6. Functionality Added or Changed * Packaging: MySQL Cluster Manager is now built and shipped with GLib-2.44.0, OpenSSL 1.0.1p, and the MySQL 5.6 client library. (Bug #22202878) * Agent: When using the import cluster command, before, if an SQL node was started at the command line with options outside of a special, pre-defined set, the import would fail with the complaint that those options were unsupported. Now, import will continue in the situation, as long as those options and their values also appear in the node's configuration created by MySQL Cluster Manager for import. (Bug #21943518) * Agent: A warning is now logged (if log-level=warning) when a failed process is not restarted because the parameter StopOnError has the value "true." (Bug #21575241) * Agent: Two new options have been introduced for the upgrade cluster command: --retry and --nodeid. They, together with the --force option, allow a retry after an initial attempt to upgrade a cluster has failed. See description for upgrade cluster for detail. (Bug #20469067, Bug #16932006, Bug #21200698) * Client: The get command now returns attributes in the same order as the MySQL Cluster ndb_mgmd command does when the --print-full-config option is used, with the non-data nodes going first, and in increasing order of the node ID. (Bug #22202973) * Client: A new autotune command has been introduced, which tunes a number of parameters of the cluster to optimize its performance. (Bug #22202855) * Client: The show settings command has a new --hostinfo option, with which the command prints out information on the host the mcm client is connected to. (Bug #21923561) * Client: You can now use the wildcard * (asterisk character) to match attribute names in a get command. See The get Command (http://dev.mysql.com/doc/mysql-cluster-manager/1.4/en/mc m-get.html) for examples. (Bug #18069656) Bugs Fixed * Agent: On Windows platform, after a cluster import, the subsequent cluster restart would time out if a non-default value of the option pid_file has been imported for a mysqld node. (Bug #21943518) References: This bug is a regression of Bug #2944. * Agent: When a data node could not be restarted after a set command because some attributes were set wrongly, another set command could not be used to correct the attributes, because the set command required the data node to be running. With this fix, the second set command can now be executed even when the data node is not running, as long as the --force option is used. The failed node is then restarted, followed by a rolling restart of the cluster. (Bug #21943518) * Agent: A timeout occurred for a restore cluster command when the number of tables in the cluster was huge (>1000). It was because a timeout extension was blocked. This fix unblocks the extension. (Bug #21393857) * Agent: At the initial startup of a large cluster (with memory size in the order of 10GB), the process might time out while waiting for a data node to start. This fix makes the transaction timeout longer for data node initiation. (Bug #21355383) * Agent: Under some conditions, a check status command might report negative node group ID values for processes after an add process command was completed. That was because the agent was reporting the node group IDs before their proper values had arrived, after the creation of new node groups. This fix makes the agent wait for the correct node group IDs before r
MySQL Cluster 7.4.8 has been released
Dear MySQL Users, MySQL Cluster 7.4.8 (General Availability) is a new release for MySQL Cluster 7.4. 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.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.8 DMR can be downloaded from the "Development Releases" tab at 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. As with any other pre-production release, caution should be taken when installing on production level systems or systems with critical data. More information on the Development Milestone Release process can be found at http://dev.mysql.com/doc/mysql-development-cycle/en/development-milestone-releases.html More details can be found at http://www.mysql.com/products/cluster/ Enjoy ! Changes in MySQL Cluster NDB 7.4.8 (5.6.27-ndb-7.4.8 2015-10-16) MySQL Cluster NDB 7.4.8 is a new release of MySQL 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 MySQL Cluster releases. Obtaining MySQL Cluster NDB 7.4. MySQL Cluster NDB 7.4 source code and binaries can be obtained from http://dev.mysql.com/downloads/cluster/. For an overview of changes made in MySQL Cluster NDB 7.4, see MySQL Cluster Development in MySQL Cluster NDB 7.4 (http://dev.mysql.com/doc/refman/5.6/en/mysql-cluster-develop ment-5-6-ndb-7-4.html). This release also incorporates all bugfixes and changes made in previous MySQL Cluster releases, as well as all bugfixes and feature changes which were added in mainline MySQL 5.6 through MySQL 5.6.27 (see Changes in MySQL 5.6.27 (2015-09-30) (http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-27.h tml)). Functionality Added or Changed * Important Change; Cluster Replication: Added the create_old_temporals server system variable to compliment the system variables avoid_temporal_upgrade and show_old_temporals introduced in MySQL 5.6.24 and available in MySQL Cluster beginning with NDB 7.3.9 and NDB 7.4.6. Enabling create_old_temporals causes mysqld to use the storage format employed prior to MySQL 5.6.4 when creating any DATE, DATETIME, or TIMESTAMP column---that is, the column is created without any support for fractional seconds. create_old_temporals is disabled by default. The system variable is read-only; to enable the use of pre-5.6.4 temporal types, set the equivalent option (--create-old-temporals) on the command line, or in an option file read by the MySQL server. create_old_temporals is available only in MySQL Cluster; it is not supported in the standard MySQL 5.6 server. It is intended to facilitate upgrades from MySQL Cluster NDB 7.2 to MySQL Cluster NDB 7.3 and 7.4, after which table columns of the affected types can be upgraded to the new storage format. create_old_temporals is deprecated and scheduled for removal in a future version of MySQL Cluster. avoid_temporal_upgrade must also be enabled for this feature to work properly. You should also enable show_old_temporals as well. For more information, see the descriptions of these variables. For more about the changes in MySQL's temporal types, see Storage Requirements for Date and Time Types (http://dev.mysql.com/doc/refman/5.6/en/storage-requireme nts.html#data-types-storage-reqs-date-time). (Bug #20701918) References: See also Bug #21492598, Bug #72997, Bug #18985760. * When the --database option has not been specified for ndb_show_tables, and no tables are found in the TEST_DB database, an appropriate warning message is now issued. (Bug #78379, Bug #11758430) Bugs Fixed * Important Change: When ndb_restore was run without --disable-indexes or --rebuild-indexes on
MySQL Cluster 7.2.22 has been released
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 and Memcached) MySQL Cluster 7.2.22, 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.2/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 Cluster NDB 7.2.22 (5.5.46-ndb-7.2.22) (2015-10-19) MySQL Cluster NDB 7.2.22 is a new release of MySQL Cluster, incorporating new features in the NDB storage engine, and fixing recently discovered bugs in previous MySQL Cluster NDB 7.2 development releases. Obtaining MySQL Cluster NDB 7.2. MySQL Cluster NDB 7.2 source code and binaries can be obtained from http://dev.mysql.com/downloads/cluster/. This release also incorporates all bugfixes and changes made in previous MySQL Cluster releases, as well as all bugfixes and feature changes which were added in mainline MySQL 5.5 through MySQL 5.5.46 (see Changes in MySQL 5.5.46 (2015-09-30) (http://dev.mysql.com/doc/relnotes/mysql/5.5/en/news-5-5-46.html)). Bugs Fixed * Backup block states were reported incorrectly during backups. (Bug #21360188) References: See also Bug #20204854, Bug #21372136. * When a data node is known to have been alive by other nodes in the cluster at a given global checkpoint, but its sysfile reports a lower GCI, the higher GCI is used to determine which global checkpoint the data node can recreate. This caused problems when the data node being started had a clean file system (GCI = 0), or when it was more than more global checkpoint behind the other nodes. Now in such cases a higher GCI known by other nodes is used only when it is at most one GCI ahead. (Bug #19633824) References: See also Bug #20334650, Bug #2183. This bug was introduced by Bug #29167. * After restoring the database schema from backup using ndb_restore, auto-discovery of restored tables in transactions having multiple statements did not work correctly, resulting in Deadlock found when trying to get lock; try restarting transaction errors. This issue was encountered both in the mysql client, as well as when such transactions were executed by application programs using Connector/J and possibly other MySQL APIs. Prior to upgrading, this issue can be worked around by executing SELECT TABLE_NAME, TABLE_SCHEMA FROM INFORMATION_SCHEMA.TABLES WHERE ENGINE = 'NDBCLUSTER' on all SQL nodes following the restore operation, before executing any other statements. (Bug #18075170) * ndb_desc used with the --extra-partition-info and --blob-info options failed when run against a table containing one or more TINYBLOB. columns. (Bug #14695968) * Cluster API: The internal value representing the latest global checkpoint was not always updated when a completed epoch of event buffers was inserted into the event queue. This caused subsequent calls to Ndb::pollEvents() and pollEvents2() to fail when trying to obtain the correct GCI for the events available in the event buffers. This could also result in later calls to nextEvent() or nextEvent2() seeing events that had not yet been discovered. (Bug #78129, Bug #21651536) * Cluster API: While executing dropEvent(), if the coordinator DBDICT failed after the subscription manager (SUMA block) had removed all subscriptions but before the coordinator had deleted the event from the system table, the dropped event remained in the table, causing any subsequent drop or create event with the same name to fail with NDB error 1419 Subscription already dropped or error 746 Event name already exists. This occurred even when calling dropEvent() with a nonzero force argument. Now in such cases, error 1419 is ignored, and DBDICT deletes the event from the table. (Bug #21554676) -- MySQL General Mailing List For list archives:
MySQL Cluster 7.4.8 has been released
Dear MySQL Users, MySQL Cluster 7.4.8 (Milestone Release) is a public milestone release for MySQL Cluster 7.4. 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.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.8 DMR can be downloaded from the "Development Releases" tab at 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. As with any other pre-production release, caution should be taken when installing on production level systems or systems with critical data. More information on the Development Milestone Release process can be found at http://dev.mysql.com/doc/mysql-development-cycle/en/development-milestone-releases.html More details can be found at http://www.mysql.com/products/cluster/ Enjoy ! Changes in MySQL Cluster NDB 7.4.8 (5.6.27-ndb-7.4.8 2015-10-16) MySQL Cluster NDB 7.4.8 is a new release of MySQL 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 MySQL Cluster releases. Obtaining MySQL Cluster NDB 7.4. MySQL Cluster NDB 7.4 source code and binaries can be obtained from http://dev.mysql.com/downloads/cluster/. For an overview of changes made in MySQL Cluster NDB 7.4, see MySQL Cluster Development in MySQL Cluster NDB 7.4 (http://dev.mysql.com/doc/refman/5.6/en/mysql-cluster-develop ment-5-6-ndb-7-4.html). This release also incorporates all bugfixes and changes made in previous MySQL Cluster releases, as well as all bugfixes and feature changes which were added in mainline MySQL 5.6 through MySQL 5.6.27 (see Changes in MySQL 5.6.27 (2015-09-30) (http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-27.h tml)). Functionality Added or Changed * Important Change; Cluster Replication: Added the create_old_temporals server system variable to compliment the system variables avoid_temporal_upgrade and show_old_temporals introduced in MySQL 5.6.24 and available in MySQL Cluster beginning with NDB 7.3.9 and NDB 7.4.6. Enabling create_old_temporals causes mysqld to use the storage format employed prior to MySQL 5.6.4 when creating any DATE, DATETIME, or TIMESTAMP column---that is, the column is created without any support for fractional seconds. create_old_temporals is disabled by default. The system variable is read-only; to enable the use of pre-5.6.4 temporal types, set the equivalent option (--create-old-temporals) on the command line, or in an option file read by the MySQL server. create_old_temporals is available only in MySQL Cluster; it is not supported in the standard MySQL 5.6 server. It is intended to facilitate upgrades from MySQL Cluster NDB 7.2 to MySQL Cluster NDB 7.3 and 7.4, after which table columns of the affected types can be upgraded to the new storage format. create_old_temporals is deprecated and scheduled for removal in a future version of MySQL Cluster. avoid_temporal_upgrade must also be enabled for this feature to work properly. You should also enable show_old_temporals as well. For more information, see the descriptions of these variables. For more about the changes in MySQL's temporal types, see Storage Requirements for Date and Time Types (http://dev.mysql.com/doc/refman/5.6/en/storage-requireme nts.html#data-types-storage-reqs-date-time). (Bug #20701918) References: See also Bug #21492598, Bug #72997, Bug #18985760. * When the --database option has not been specified for ndb_show_tables, and no tables are found in the TEST_DB database, an appropriate warning message is now issued. (Bug #78379, Bug #11758430) Bugs Fixed * Important Change: When ndb_restore was run without --disable-indexes or --rebuild-inde
MySQL Cluster 7.3.10 has been released
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.3.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. The release notes are available from http://dev.mysql.com/doc/relnotes/mysql-cluster/7.3/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 Cluster NDB 7.3.10 (5.6.25-ndb-7.3.10) (2015-07-13) MySQL Cluster NDB 7.3.10 is a new release of MySQL Cluster, based on MySQL Server 5.6 and including features from version 7.3 of the NDB storage engine, as well as fixing a number of recently discovered bugs in previous MySQL Cluster releases. Obtaining MySQL Cluster NDB 7.3. MySQL Cluster NDB 7.3 source code and binaries can be obtained from http://dev.mysql.com/downloads/cluster/. For an overview of changes made in MySQL Cluster NDB 7.3, see MySQL Cluster Development in MySQL Cluster NDB 7.3 (http://dev.mysql.com/doc/refman/5.6/en/mysql-cluster-develop http://dev.mysql.com/doc/refman/5.6/en/mysql-cluster-development-5-6-ndb-7-3.html ment-5-6-ndb-7-3.html http://dev.mysql.com/doc/refman/5.6/en/mysql-cluster-development-5-6-ndb-7-3.html). This release also incorporates all bugfixes and changes made in previous MySQL Cluster releases, as well as all bugfixes and feature changes which were added in mainline MySQL 5.6 through MySQL 5.6.25 (see Changes in MySQL 5.6.25 (2015-05-29) (http://dev.mysql.com/doc/relnotes/mysql/5.6/en/ http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-25.html news-5-6-25.html http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-25.html)). Functionality Added or Changed * ClusterJ: Under high workload, it was possible to overload the direct memory used to back domain objects, because direct memory is not garbage collected in the same manner as objects allocated on the heap. Two strategies have been added to the ClusterJ implementation: first, direct memory is now pooled, so that when the domain object is garbage collected, the direct memory can be reused by another domain object. Additionally, a new user-level method, release(instance), has been added to the Session interface, which allows users to release the direct memory before the corresponding domain object is garbage collected. See the description for release(instance) http://dev.mysql.com/doc/ndbapi/en/mccj-clusterj-session.html#mccj-clusterj-session-release-t for more information. (Bug #20504741) Bugs Fixed * Important Change; Cluster API: Added the method Ndb::isExpectingHigherQueuedEpochs() to the NDB API to detect when additional, newer event epochs were detected by pollEvents2(). The behavior of Ndb::pollEvents() has also been modified such that it now returns NDB_FAILURE_GCI (equal to ~(Uint64) 0) when a cluster failure has been detected. (Bug #18753887) * After restoring the database metadata (but not any data) by running ndb_restore --restore_meta (or -m), SQL nodes would hang while trying to SELECT from a table in the database to which the metadata was restored. In such cases the attempt to query the table now fails as expected, since the table does not actually exist until ndb_restore is executed with --restore_data (-r). (Bug #21184102) References: See also Bug #16890703. * When a great many threads opened and closed blocks in the NDB API in rapid succession, the internal close_clnt() function synchronizing the closing of the blocks waited an insufficiently long time for a self-signal indicating potential additional signals needing to be processed. This led to excessive CPU usage by ndb_mgmd, and prevented other threads from opening or closing other blocks. This issue is fixed by changing the function polling call to wait on a specific condition to be woken up (that is, when a signal has in fact been executed). (Bug #21141495) * Previously, multiple send threads could be invoked for handling sends to the same node; these threads then competed for the same send lock
MySQL Cluster 7.2.19 has been released
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 and Memcached) MySQL Cluster 7.2.19, 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.2/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 Cluster NDB 7.2.19 (5.5.41-ndb-7.2.19) (2015-01-25) MySQL Cluster NDB 7.2.19 is a new release of MySQL Cluster, incorporating new features in the NDB storage engine, and fixing recently discovered bugs in previous MySQL Cluster NDB 7.2 development releases. Obtaining MySQL Cluster NDB 7.2. MySQL Cluster NDB 7.2 source code and binaries can be obtained from http://dev.mysql.com/downloads/cluster/. This release also incorporates all bugfixes and changes made in previous MySQL Cluster releases, as well as all bugfixes and feature changes which were added in mainline MySQL 5.5 through MySQL 5.5.41 (see Changes in MySQL 5.5.41 2014-11-28 http://dev.mysql.com/doc/relnotes/mysql/5.5/en/news-5-5-41.html). Bundled SSL Update (Commercial Releases) * Starting with this release, commercial distributions of MySQL Cluster NDB 7.2 are built using OpenSSL 1.0.1i. Bugs Fixed * The global checkpoint commit and save protocols can be delayed by various causes, including slow disk I/O. The DIH master node monitors the progress of both of these protocols, and can enforce a maximum lag time during which the protocols are stalled by killing the node responsible for the lag when it reaches this maximum. This DIH master GCP monitor mechanism did not perform its task more than once per master node; that is, it failed to continue monitoring after detecting and handling a GCP stop. (Bug #20128256) References: See also Bug #19858151. * A number of problems relating to the fired triggers pool have been fixed, including the following issues: + When the fired triggers pool was exhausted, NDB returned Error 218 (Out of LongMessageBuffer). A new error code 221 is added to cover this case. + An additional, separate case in which Error 218 was wrongly reported now returns the correct error. + Setting low values for MaxNoOfFiredTriggers led to an error when no memory was allocated if there was only one hash bucket. + An aborted transaction now releases any fired trigger records it held. Previously, these records were held until its ApiConnectRecord was reused by another transaction. + In addition, for the Fired Triggers pool in the internal ndbinfo.ndb$pools table, the high value always equalled the total, due to the fact that all records were momentarily seized when initializing them. Now the high value shows the maximum following completion of initialization. (Bug #19976428) * Online reorganization when using ndbmtd data nodes and with binary logging by mysqld enabled could sometimes lead to failures in the TRIX and DBLQH kernel blocks, or in silent data corruption. (Bug #19903481) References: See also Bug #19912988. * The local checkpoint ScanFrag watchdog and the global checkpoint monitor can each exclude a node when it is too slow when participating in their respective protocols. This exclusion was implemented by simply asking the failing node to shut down, which in case this was delayed (for whatever reason) could prolong the duration of the GCP or LCP stall for other, unaffected nodes. To minimize this time, an isolation mechanism has been added to both protocols whereby any other live nodes forcibly disconnect the failing node after a predetermined amount of time. This allows the failing node the opportunity to shut down gracefully (after logging debugging and other information) if possible, but limits the time that other nodes must wait for this to occur. Now, once the remaining live
MySQL Cluster 7.3.8 has been released
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.3.8 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.3/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 Cluster NDB 7.3.8 (5.6.22-ndb-7.3.8) (2015-01-21) MySQL Cluster NDB 7.3.8 is a new release of MySQL Cluster, based on MySQL Server 5.6 and including features from version 7.3 of the NDB storage engine, as well as fixing a number of recently discovered bugs in previous MySQL Cluster releases. Obtaining MySQL Cluster NDB 7.3. MySQL Cluster NDB 7.3 source code and binaries can be obtained from http://dev.mysql.com/downloads/cluster/. For an overview of changes made in MySQL Cluster NDB 7.3, see MySQL Cluster Development in MySQL Cluster NDB 7.3 ( http://dev.mysql.com/doc/refman/5.6/en/mysql-cluster-development-5-6-ndb-7-3.html ). This release also incorporates all bugfixes and changes made in previous MySQL Cluster releases, as well as all bugfixes and feature changes which were added in mainline MySQL 5.6 through MySQL 5.6.22 (see Changes in MySQL 5.6.22 (2014-12-01) ( http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-22.html )). Functionality Added or Changed * Performance: Recent improvements made to the multithreaded scheduler were intended to optimize the cache behavior of its internal data structures, with members of these structures placed such that those local to a given thread do not overflow into a cache line which can be accessed by another thread. Where required, extra padding bytes are inserted to isolate cache lines owned (or shared) by other threads, thus avoiding invalidation of the entire cache line if another thread writes into a cache line not entirely owned by itself. This optimization improved MT Scheduler performance by several percent. It has since been found that the optimization just described depends on the global instance of struct thr_repository starting at a cache line aligned base address as well as the compiler not rearranging or adding extra padding to the scheduler struct; it was also found that these prerequisites were not guaranteed (or even checked). Thus this cache line optimization has previously worked only when g_thr_repository (that is, the global instance) ended up being cache line aligned only by accident. In addition, on 64-bit platforms, the compiler added extra padding words in struct thr_safe_pool such that attempts to pad it to a cache line aligned size failed. The current fix ensures that g_thr_repository is constructed on a cache line aligned address, and the constructors modified so as to verify cacheline aligned adresses where these are assumed by design. Results from internal testing show improvements in MT Scheduler read performance of up to 10% in some cases, following these changes. (Bug #18352514) * Cluster API: Two new example programs, demonstrating reads and writes of CHAR, VARCHAR, and VARBINARY column values, have been added to storage/ndb/ndbapi-examples in the MySQL Cluster source tree. For more information about these programs, including source code listings, see NDB API Simple Array Example ( http://dev.mysql.com/doc/ndbapi/en/ndbapi-examples-array-simple.html ) , and NDB API Simple Array Example Using Adapter ( http://dev.mysql.com/doc/ndbapi/en/ndbapi-examples-array-adapter.html ). Bugs Fixed * The global checkpoint commit and save protocols can be delayed by various causes, including slow disk I/O. The DIH master node monitors the progress of both of these protocols, and can enforce a maximum lag time during which the protocols are stalled by killing the node responsible for the lag when it reaches this maximum
MySQL Cluster Manager 1.3.3 has been released
Dear MySQL users, MySQL Cluster Manager 1.3.3, has been released and can be downloaded from the My Oracle Support (MOS) website. It will also be available on Oracle Software Delivery Cloud at http://edelivery.oracle.com with the next monthly update. MySQL Cluster Manager is an optional component of the MySQL Cluster Carrier Grade Edition, providing a command-line interface that automates common management tasks, including the following online operations: - Configuring and starting MySQL Cluster - Upgrades - Addition of new nodes - Configuration changes - Backup and restore MySQL Cluster Manager is a commercial extension to the MySQL family of products. More details can be found at http://www.mysql.com/products/cluster/mcm/ A brief summary of changes in MySQL Cluster Manager version 1.3.3 is listed below: Changes in MySQL Cluster Manager 1.3.3 (2014-12-01) This section documents all changes and bug fixes that have been applied in MySQL Cluster Manager 1.3.3 since the release of MySQL Cluster Manager version 1.3.0. Functionality Added or Changed * Agent: For a node on which an expected backup is not found, the output for the list backups command now reads None for BackupId and says No backups. (Bug #19208671) * A remove process command has been added, providing a means to perform an offline scale down for a cluster. See Section 4.6.6, The remove process Command, for details. Bugs Fixed * Agent: When a cluster was in single-user mode, any mcm command that causes a configuration change and a subsequent rolling restart (for example a set, add process, or a restart cluster) would stop the first data node in each nodegroup and would then be unable to restart it, due to a limitation with the MySQL Cluster. With this fix, mcm rejects those commands under the situation with an error message, instead of letting the data nodes be stopped. (Bug #20026523) * Agent: When MySQL Cluster Manager was trying to create a temporary directory (tmpdir) for a MySQL node under its directory for manager data (manager-dir), it did not always follow the specification for manager-dir for the node, which resulted in putting the temporary directory at the wrong location sometimes. (Bug #20026523) * Agent: When the --log-use-syslog option was set during the startup of mcmd, an error was thrown, complaining that the option log-file was also used (which is not allowed) even if --log-file was not really set. (Bug #19972864) * Agent: If a data node went from the running into the added state for some reasons, it became irrecoverable by MySQL Cluster Manager because, as a safeguard, MySQL Cluster Manager did not start a newly added data node automatically when the cluster was running. The safeguard is now removed, in order to allow the recovery of a data node in the described situation. (Bug #19787156) * Agent: During the recovery of an mcmd agent from a crash, if the cluster's management node could not be contacted for information, the agent just reported the statuses of the managed processes as they were last known, which might not reflect the processes' real statuses (for example, a process might have just crashed, and the agent would still said it is running), With this fix, the mcmd agent will report the statuses of the processes as unknown in the described situation. (Bug #19321446) * Agent: When bootstrapping a default cluster with the --bootstrap option, the ndbd process was used for data nodes. With this fix, the multi-threaded ndbmtd process is used instead, which is preferable from a performance perspective. (Bug #18068338) * Agent: An mcmd agent crashed when trying to stop a cluster that was hanging during an operation to restore itself. (Bug #17957393) * Agent: Configuration attribute values that start and end with double quotes could not be set using the set command. (Bug #13040122) * Client: When setting the LogDestination configuration attribute using the set command, mcm threw a syntax error when the attribute's value was single-quoted. (Bug #19435351) * Client: The error reporting for a data node crash by the MySQL Cluster Manager client did not include what had been reported by the ALERT statements before. With this fix, ALERT is included as a matching pattern for picking up errors from logs of the data nodes, which might result in more information on the crash being provided. (Bug #19426279) * Client: At an attempt to add to a site a host that already belonged to another site, the MySQL Cluster Manager client hung; and even after the client
MySQL Cluster 7.4.2 has been released
Dear MySQL Users, MySQL Cluster 7.4.2 (Milestone Release) is a public milestone release for MySQL Cluster 7.4. 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.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.2 DMR can be downloaded from the Development Releases tab at 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. As with any other pre-production release, caution should be taken when installing on production level systems or systems with critical data. More information on the Development Milestone Release process can be found at http://dev.mysql.com/doc/mysql-development-cycle/en/development-milestone-releases.html More details can be found at http://www.mysql.com/products/cluster/ Enjoy ! == Changes in MySQL Cluster NDB 7.4.2 (5.6.21-ndb-7.4.2 2014-11-05) MySQL Cluster NDB 7.4.2 is a new release of MySQL Cluster, based on MySQL Server 5.6 and including features under development for version 7.4 of the NDB storage engine, as well as fixing a number of recently discovered bugs in previous MySQL Cluster releases. Obtaining MySQL Cluster NDB 7.4. MySQL Cluster NDB 7.4 source code and binaries can be obtained from http://dev.mysql.com/downloads/cluster/. For an overview of changes made in MySQL Cluster NDB 7.4, see MySQL Cluster Development in MySQL Cluster NDB 7.4 (http://dev.mysql.com/doc/refman/5.6/en/mysql-cluster-development-5-6-ndb-7-4.html). This release also incorporates all bugfixes and changes made in previous MySQL Cluster releases, as well as all bugfixes and feature changes which were added in mainline MySQL 5.6 through MySQL 5.6.21 (see Changes in MySQL 5.6.21 (2014-09-23) (http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-21.html). Functionality Added or Changed * After adding new data nodes to the configuration file of a MySQL Cluster having many API nodes, but prior to starting any of the data node processes, API nodes tried to connect to these missing data nodes several times per second, placing extra loads on management nodes and the network. To reduce unnecessary traffic caused in this way, it is now possible to control the amount of time that an API node waits between attempts to connect to data nodes which fail to respond; this is implemented in two new API node configuration parameters StartConnectBackoffMaxTime and ConnectBackoffMaxTime. Time elapsed during node connection attempts is not taken into account when applying these parameters, both of which are given in milliseconds with approximately 100 ms resolution. As long as the API node is not connected to any data nodes as described previously, the value of the StartConnectBackoffMaxTime parameter is applied; otherwise, ConnectBackoffMaxTime is used. In a MySQL Cluster with many unstarted data nodes, the values of these parameters can be raised to circumvent connection attempts to data nodes which have not yet begun to function in the cluster, as well as moderate high traffic to management nodes. For more information about the behavior of these parameters, see Defining SQL and Other API Nodes in a MySQL Cluster (http://dev.mysql.com/doc/refman/5.6/en/mysql-cluster-api-definition.html). (Bug#17257842) Bugs Fixed * Online downgrades to MySQL Cluster NDB 7.3 failed when a MySQL Cluster NDB 7.4 master attempted to request a local checkpoint with 32 fragments from a data node already running NDB 7.3, which supports only 2 fragments for LCPs. Now in such cases, the NDB 7.4 master determines how many fragments the data node can handle before making the request. (Bug#19600834) * The server side of an NDB transporter disconnected
MySQL Cluster 7.1.33 has been released
Dear MySQL users, MySQL Cluster is the distributed, shared-nothing variant of MySQL. This storage engine provides: - Real-time performance based on in-memory storage (with checkpointing to disk) - Read write scalability through transparent auto-sharding - 99.999% High Availability with no single point of failure and on-line maintenance - SQL and NoSQL API (including C++, Java, and http) - Active-Active/Multi-Master geographic replication MySQL Cluster 7.1.33, 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.1/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 Cluster NDB 7.1.33 (5.1.73-ndb-7.1.33) (2014-10-21) MySQL Cluster NDB 7.1.33 is a new release of MySQL Cluster, incorporating new features in the NDB storage engine and fixing recently discovered bugs in previous MySQL Cluster NDB 7.1 releases. The latest MySQL Cluster NDB 7.1 binaries for supported platforms can be obtained from http://dev.mysql.com/downloads/cluster/. Source code for the latest MySQL Cluster NDB 7.1 release can be obtained from the same location. You can also access the MySQL Cluster NDB 7.1 development source tree at https://code.launchpad.net/~mysql/mysql-server/cluster-7.1 This release also incorporates all bugfixes and changes made in previous MySQL Cluster releases, as well as all bugfixes and feature changes which were added in mainline MySQL 5.1 through MySQL 5.1.73 (see Changes in MySQL 5.1.73 (2013-12-03) (http://dev.mysql.com/doc/relnotes/mysql/5.1/en/news-5-1-73.html)) . Functionality Added or Changed * Added the --exclude-missing-tables option for ndb_restore. When enabled, the option causes tables present in the backup but not in the target database to be ignored. (Bug #57566, Bug #11764704) Bugs Fixed * When assembling error messages of the form Incorrect state for node n state: node_state, written when the transporter failed to connect, the node state was used in place of the node ID in a number of instances, which resulted in errors of this type for which the node state was reported incorrectly. (Bug #19559313, Bug #73801) * In some cases, transporter receive buffers were reset by one thread while being read by another. This happened when a race condition occurred between a thread receiving data and another thread initiating disconnect of the transporter (disconnection clears this buffer). Concurrency logic has now been implemented to keep this race from taking place. (Bug #19554279, Bug #73656) * A more detailed error report is printed in the event of a critical failure in one of the NDB internal sendSignal*() methods, prior to crashing the process, as was already implemented for sendSignal(), but was missing from the more specialized sendSignalNoRelease() method. Having a crash of this type correctly reported can help with identifying configuration hardware issues in some cases. (Bug #19414511) References: See also Bug #19390895. * ndb_restore failed to restore the cluster's metadata when there were more than approximately 17 K data objects. (Bug #19202654) * Parallel transactions performing reads immediately preceding a delete on the same tuple could cause the NDB kernel to crash. This was more likely to occur when separate TC threads were specified using the ThreadConfig configuration parameter. (Bug #19031389) * Incorrect calculation of the next autoincrement value following a manual insertion towards the end of a cached range could result in duplicate values sometimes being used. This issue could manifest itself whne using certain combinations of values for auto_increment_increment, auto_increment_offset, and ndb_batch_prefetch_sz. This issue has been fixed by modifying this calculation to ensure that the next value from the cache as computed by NDB is of the form auto_increment_offset + (N * auto_increment_increment. This avoids any rounding up by the MySQL Server of the returned value, which could result in duplicate entries when the rounded-up value fell outside the range of values cached by NDB. (Bug #17893872) * ndb_show_tables --help output contained misleading information about the --database (-d) option. In addition, the long
MySQL Cluster 7.4.1 has been released
Dear MySQL users, MySQL Cluster 7.4.1 (Milestone Release) is the first public milestone release for MySQL Cluster 7.4. The MySQL Cluster 7.4.1 DMR can be downloaded from the Development Releases tab at http://dev.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 is the distributed, shared-nothing variant of MySQL. This storage engine provides: - Real-time performance based on in-memory storage (with checkpointing to disk) - Read write scalability through transparent auto-sharding - 99.999% High Availability with no single point of failure and on-line maintenance - SQL and NoSQL API (including C++, Java, http, Memcached and JavaScript/Node.js) - Active-Active/Multi-Master geographic replication 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. 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. As with any other pre-production release, caution should be taken when installing on production level systems or systems with critical data. More information on the Development Milestone Release process can be found at http://dev.mysql.com/doc/mysql-development-cycle/en/development-milestone-releases.html Note that 7.4.1 includes all features from MySQL Cluster 7.3. More details can be found at http://www.mysql.com/products/cluster/ Enjoy! Changes in MySQL Cluster NDB 7.4.1 (5.6.20-ndb-7.4.1 2014-09-25) MySQL Cluster NDB 7.4.1 is a new Developer Milestone release of MySQL Cluster, based on MySQL Server 5.6 and previewing new features under development for version 7.4 of the NDB storage engine. Obtaining MySQL Cluster NDB 7.4. MySQL Cluster NDB 7.4 source code and binaries can be obtained from http://dev.mysql.com/downloads/cluster/. For an overview of changes made in MySQL Cluster NDB 7.4, see MySQL Cluster Development in MySQL Cluster NDB 7.4 (http://dev.mysql.com/doc/refman/5.6/en/mysql-cluster-development-5-6-ndb-7-4.html). This release also incorporates all bugfixes and changes made in previous MySQL Cluster releases, as well as all bugfixes and feature changes which were added in mainline MySQL 5.6 through MySQL 5.6.20 (see Changes in MySQL 5.6.20 (2014-07-31) (http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-20.html)). Functionality Added or Changed * Performance: Several internal methods relating to the NDB receive thread have been optimized to make mysqld more efficient in processing SQL applications with the NDB storage engine. In particular, this work improves the performance of the NdbReceiver::execTRANSID_AI() method, which is commonly used to receive a record from the data nodes as part of a scan operation. (Since the receiver thread sometimes has to process millions of received records per second, it is critical that this method does not perform unnecessary work, or tie up resources that are not strictly needed.) The associated internal functions receive_ndb_packed_record() and handleReceivedSignal() methods have also been improved, and made more efficient. * Performance: A number of performance and other improvements have been made with regard to node starts and restarts. The following list contains a brief description of each of these changes: + Before memory allocated on startup can be used, it must be touched, causing the operating system to allocate the actual physical memory needed. The process of touching each page of memory that was allocated has now been multithreaded, with touch times on the order of 3 times shorter than with a single thread when performed by 16 threads. + When performing a node or system restart, it is necessary to restore local checkpoints for the fragments. This process previously used delayed signals at a point which was found to be critical to performance; these have now been replaced with normal (undelayed) signals, which should shorten significantly the time required to back up a MySQL Cluster or to restore it from backup. + Previously, there could be at most 2 LDM instances active with local checkpoints at any given time. Now, up to 16 LDMs can be used for performing this task, which increases utilization of available CPU power, and can speed up LCPs by a factor of 10, which in turn can greatly improve restart times. Better reporting of disk
MySQL Cluster Manager 1.3.2 has been released
Dear MySQL users, MySQL Cluster Manager 1.3.2, has been released and can be downloaded from the My Oracle Support (MOS) website. It will also be available on Oracle Software Delivery Cloud at http://edelivery.oracle.com with the September update in a few weeks. MySQL Cluster Manager is an optional component of MySQL Cluster Carrier Grade Edition - providing a command-line-interface that automates common management tasks. These include these on-line operations: - Configuring and starting MySQL Cluster - Upgrades - Addition of new nodes - Configuration changes - Backup and restore MySQL Cluster Manager is a commercial extension. More details can be found at http://www.mysql.com/products/cluster/mcm/ A brief summary of changes in MySQL Cluster Manager version 1.3.2 is listed below: Functionality Added or Changed (2014-08-15) * Agent; Client: In order to improve execution robustness, MySQL Cluster Manager now fails any commands that reconfigure a cluster with a message (i.e. ERROR 5027 Unable to perform command due to utility proc_name with pid ospid on host) if any utility process (for example, mysql_upgrade, mysql_install_db, or ndb_restore) that was started by a previous command is still remaining (running or hung) on any host when the command is issued. (Bug #18966650) * Client: MySQL Cluster Manager now throws an error if the user tries to import a cluster or a cluster configuration using the import cluster (http://dev.mysql.com/doc/mysql-cluster-manager/1.3/en/mcm-import-cluster.html) or import config (http://dev.mysql.com/doc/mysql-cluster-manager/1.3/en/mcm-import-config.html) command while the user who runs the mcmd process does not have permissions to the cluster processes' PID files. This happens typically when mcmd is started with the user mysql while the cluster is started with root. (Bug #18887139) Bugs Fixed * Agent; Client: On Windows platforms, when a data node could not be restarted during a rolling restart of the cluster, it was not reported to the user. With this fix, the user now gets a report when a maintenance restart of a data node failed. (Bug #19227535) * Agent; Client: The import config (http://dev.mysql.com/doc/mysql-cluster-manager/1.3/en/mcm-import-config.html) command did not import configuration settings from a cluster's my.cnf file properly; problems included: + Some settings in the [mysqld] section were left out (for example, key_buffer_size and query_cache_type). + Some options in the [client] section were included by mistake. + The !include and !includedir statements for including settings from other files were ignored + Quoted values were not handled properly---the quotes were taken literally. + Lines starting with ; were not treated as comments. + The option modifiers loose_ and maximum_ were not recognized. + Option group for specific release series (for example, [mysqld-5.6]) were not imported. (Bug #19078129) * Agent; Client: When the configuration of a running cluster was being imported using the import config (http://dev.mysql.com/doc/mysql-cluster-manager/1.3/en/mcm-import-config.html) command, even if the parameter ThreadConfig was not defined in the config.ini file, its value could be imported from the running node's setting for it. The imported value overrode the configuration prescribed by the MaxNoOfExecutionThreads parameter in config.ini, which is supposed to set the thread configuration when ThreadConfig is not specified in config.ini. This fix prevents the import of the value for ThreadConfig from the running node, making MySQL Cluster Manager rely on the config.ini file for the thread configuration. (Bug #19032714) * Agent; Client: The import config (http://dev.mysql.com/doc/mysql-cluster-manager/1.3/en/mcm-import-config.html) command sometimes imported MySQL server default values that were not specified in the cluster's configuration files. With this fix, no such values are imported. (Bug #18651301) * Agent; Client: When using the import config (http://dev.mysql.com/doc/mysql-cluster-manager/1.3/en/mcm-import-config.html) command, the format of an imported configuration setting was sometimes changed from that which was used in the config.ini file---for example, a value in megabytes was imported as a value in bytes and then shown as such by the get command. That made it more difficult for the user to compare the original and the imported value. This fix makes MySQL Cluster Manager follow the original format in the config.ini file when importing a cluster's configuration. (Bug #18651726) * Agent: The MySQL Cluster Manager agent might crash when running an import config (http://dev.mysql.com/doc/mysql-cluster-manager/1.3/en/mcm
MySQL Cluster 7.1.32 has been released
Dear MySQL users, MySQL Cluster is the distributed, shared-nothing variant of MySQL. This storage engine provides: - Real-time performance based on in-memory storage (with checkpointing to disk) - Read write scalability through transparent auto-sharding - 99.999% High Availability with no single point of failure and on-line maintenance - SQL and NoSQL API (including C++, Java, and http) - Active-Active/Multi-Master geographic replication MySQL Cluster 7.1.32, 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.1/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 Cluster NDB 7.1.32 (5.1.73-ndb-7.1.32) (2014-07-15) MySQL Cluster NDB 7.1.32 is a new release of MySQL Cluster, incorporating new features in the NDBCLUSTER storage engine and fixing recently discovered bugs in previous MySQL Cluster NDB 7.1 releases. Obtaining MySQL Cluster NDB 7.1. The latest MySQL Cluster NDB 7.1 binaries for supported platforms can be obtained from http://dev.mysql.com/downloads/cluster/. Source code for the latest MySQL Cluster NDB 7.1 release can be obtained from the same location. You can also access the MySQL Cluster NDB 7.1 development source tree at https://code.launchpad.net/~mysql/mysql-server/mysql-cluster-7.1. This release also incorporates all bugfixes and changes made in previous MySQL Cluster releases, as well as all bugfixes and feature changes which were added in mainline MySQL 5.1 through MySQL 5.1.73 (see Changes in MySQL 5.1.73 (2013-12-03) (http://dev.mysql.com/doc/relnotes/mysql/5.1/en/news-5-1-73.html)) . Functionality Added or Changed * Cluster API: Added as an aid to debugging the ability to specify a human-readable name for a given Ndb object and later to retrieve it. These operations are implemented, respectively, as the setNdbObjectName() and getNdbObjectName() methods. To make tracing of event handling between a user application and NDB easier, you can use the reference (from getReference() followed by the name (if provided) in printouts; the reference ties together the application Ndb object, the event buffer, and the NDB storage engine's SUMA block. (Bug #18419907) Bugs Fixed * Processing a NODE_FAILREP signal that contained an invalid node ID could cause a data node to fail. (Bug #18993037, Bug #73015) References: This bug is a regression of Bug #16007980. * ndbmtd supports multiple parallel receiver threads, each of which performs signal reception for a subset of the remote node connections (transporters) with the mapping of remote_nodes to receiver threads decided at node startup. Connection control is managed by the multi-instance TRPMAN block, which is organized as a proxy and workers, and each receiver thread has a TRPMAN worker running locally. The QMGR block sends signals to TRPMAN to enable and disable communications with remote nodes. These signals are sent to the TRPMAN proxy, which forwards them to the workers. The workers themselves decide whether to act on signals, based on the set of remote nodes they manage. The current isuue arises because the mechanism used by the TRPMAN workers for determining which connections they are responsible for was implemented in such a way that each worker thought it was responsible for all connections. This resulted in the TRPMAN actions for OPEN_COMORD, ENABLE_COMREQ, and CLOSE_COMREQ being processed multiple times. The fix keeps TRPMAN instances (receiver threads) executing OPEN_COMORD, ENABLE_COMREQ and CLOSE_COMREQ requests. In addition, the correct TRPMAN instance is now chosen when routing from this instance for a specific remote connection. (Bug #18518037) * Executing ALTER TABLE ... REORGANIZE PARTITION after increasing the number of data nodes in the cluster from 4 to 16 led to a crash of the data nodes. This issue was shown to be a regression caused by previous fix which added a new dump handler using a dump code that was already in use (7019), which caused the command to execute two different handlers with different semantics. The new handler was assigned a new DUMP code (7024). (Bug #18550318) References: This bug is a regression of Bug #14220269. * A local checkpoint (LCP) is tracked using a global LCP state (c_lcpState), and each NDB table has a status indicator which indicates the LCP status of that table (tabLcpStatus). If the global LCP state
MySQL Cluster 7.3.6 has been released
Dear MySQL users, MySQL Cluster is the distributed, shared-nothing variant of MySQL. This storage engine provides: - Real-time performance based on in-memory storage (with checkpointing to disk) - Read write scalability through transparent auto-sharding - 99.999% High Availability with no single point of failure and on-line maintenance - SQL and NoSQL API (including C++, Java, http, Memcached and JavaScript/Node.js) - Active-Active/Multi-Master geographic replication MySQL Cluster 7.3.6, 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.3/en/mysql-cluster-news-5-6-19-ndb-7-3-6.html http://dev.mysql.com/doc/relnotes/mysql-cluster/7.3/en/mysql-cluster-news-5-6-17-ndb-7-3-5.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 Cluster NDB 7.3.6 (5.6.19-ndb-7.3.6) (2014-07-11) MySQL Cluster NDB 7.3.6 is a new release of MySQL Cluster, based on MySQL Server 5.6 and including features from version 7.3 of the NDB storage engine, as well as fixing a number of recently discovered bugs in previous MySQL Cluster releases. Obtaining MySQL Cluster NDB 7.3. MySQL Cluster NDB 7.3 source code and binaries can be obtained from http://dev.mysql.com/downloads/cluster/. For an overview of changes made in MySQL Cluster NDB 7.3, see MySQL Cluster Development in MySQL Cluster NDB 7.3 (http://dev.mysql.com/doc/refman/5.6/en/mysql-cluster-development- 5-6-ndb-7-3.html). This release also incorporates all bugfixes and changes made in previous MySQL Cluster releases, as well as all bugfixes and feature changes which were added in mainline MySQL 5.6 through MySQL 5.6.19 (see Changes in MySQL 5.6.19 (2014-05-30) (http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-19.html)). Functionality Added or Changed * Cluster API: Added as an aid to debugging the ability to specify a human-readable name for a given Ndb object and later to retrieve it. These operations are implemented, respectively, as the setNdbObjectName() and getNdbObjectName() methods. To make tracing of event handling between a user application and NDB easier, you can use the reference (from getReference() followed by the name (if provided) in printouts; the reference ties together the application Ndb object, the event buffer, and the NDB storage engine's SUMA block. (Bug #18419907) Bugs Fixed * Cluster API: When two tables had different foreign keys with the same name, ndb_restore considered this a name conflict and failed to restore the schema. As a result of this fix, a slash character (/) is now expressly disallowed in foreign key names, and the naming format parent_id/child_id/fk_name is now enforced by the NDB API. (Bug #18824753) * Processing a NODE_FAILREP signal that contained an invalid node ID could cause a data node to fail. (Bug #18993037, Bug #73015) References: This bug is a regression of Bug #16007980. * When building out of source, some files were written to the source directory instead of the build dir. These included the manifest.mf files used for creating ClusterJ jars and the pom.xml file used by mvn_install_ndbjtie.sh. In addition, ndbinfo.sql was written to the build directory, but marked as output to the source directory in CMakeLists.txt. (Bug #18889568, Bug #72843) * Adding a foreign key failed with NDB Error 208 if the parent index was parent table's primary key, the primary key was not on the table's initial attributes, and the child table was not empty. (Bug #18825966) * When an NDB table served as both the parent table and a child table for 2 different foreign keys having the same name, dropping the foreign key on the child table could cause the foreign key on the parent table to be dropped instead, leading to a situation in which it was impossible to drop the remaining foreign key. This situation can be modelled using the following CREATE TABLE statements: CREATE TABLE parent ( id INT NOT NULL, PRIMARY KEY (id) ) ENGINE=NDB; CREATE TABLE child ( id INT NOT NULL, parent_id INT, PRIMARY KEY (id), INDEX par_ind (parent_id), FOREIGN KEY (parent_id) REFERENCES parent(id) ) ENGINE=NDB; CREATE TABLE grandchild ( id INT
MySQL Cluster Manager 1.3.1 has been released
Dear MySQL users, MySQL Cluster Manager 1.3.1, has been released and can be downloaded from Oracle Software Delivery Cloud at http://edelivery.oracle.com. It is also available for download from the My Oracle Support (MOS) website. MySQL Cluster Manager is an optional component of MySQL Cluster Carrier Grade Edition - providing a command-line-interface that automates common management tasks. These include these on-line operations: - Configuring and starting MySQL Cluster - Upgrades - Addition of new nodes - Configuration changes - Backup and restore MySQL Cluster Manager is a commercial extension. More details can be found at http://www.mysql.com/products/cluster/mcm/ A brief summary of changes in MySQL Cluster Manager version 1.3.1 is listed below: Functionality Added or Changed * Client; Important Change: Added the import config command. This command simplifies the process of importing a previously autonomous MySQL Cluster into MySQL Cluster Manager by importing automatically most of the cluster's configuration data into the cluster definition that has been created as part of the import process, eliminating the need for reading of configuration files and SHOW VARIABLES output and issuing of most set commands needed to prepare a cluster for import. This command also supports a --dryrun option (short form: -y) for testing purposes. You should note that any nonstandard ports used by ndb_mgmd or mysqld processes in the existing MySQL Cluster must be configured manually (using set) for the corresponding processes in the target cluster before trying to use import cluster to import the wild cluster's data. For more information, see The import config Command (http://dev.mysql.com/doc/mysql-cluster-manager/1.3/en/mcm-import-config.html), and Importing MySQL Clusters into MySQL Cluster Manager (http://dev.mysql.com/doc/mysql-cluster-manager/1.3/en/mcm-using-import-cluster.html). * Client: The --import option for create cluster now enables assignment of node ID values less than 49 for ndb_mgmd, mysqld, and ndbapi processes. The create cluster command used without this option continues to enforce the rule that processes that are not data node processes must have node IDs greater than 48. (Bug #18181039) Bugs Fixed * Agent: When executing backup cluster and abort backup with --waitstarted commands in succession, it was possible in some circumstances for the agent to use the wrong backup ID internally. (Bug #18027413) * Client: After performing an initial start of a cluster, the cluster is no longer aware of any backup IDs that have previously been used. If you take a new backup of the cluster afterwards without specifying a backup ID, the cluster tries to use 1 as the ID for the first such backup, even if you restored the cluster from a backup having 1 as its ID, which results in an error. This is expected behavior, for which there are at least 2 workarounds: 1. Move or rename the backup files following the restoration. 2. Execute the backup cluster command using the --backupid option, to specify a backup ID that is not already in use. Issues arose in such cases because the error message returned was not sufficiently descriptive, and it could be difficult to determine the true nature of the problem without reading the management server and cluster log files. Now the error message returned in the mcm client makes it clear that the backup failed due to collision with an existing backup ID. (Bug #18465705) * Client: Executing the create site command using the names of one more hosts on which the MySQL Cluster Manager Agent was not running returned ERROR 1002 (00MGR): Agent on host UNKNOWN: (delivery status does not match current view) is unavailable. Now in such cases, the name of each host lacking an agent is included as part of the error message. (Bug #18200900) * Client: Attempting to set any of the mysqld configuration attributes relating to the thread pool plugin (see Thread Pool Components and Installation (http://dev.mysql.com/doc/refman/5.5/en/thread-pool-installation.html)) including thread_pool_algorithm, thread_pool_high_priority_connection, thread_pool_max_unused_threads, thread_pool_prio_kickup_timer, thread_pool_size, and thread_pool_stall_limit---failed with the error No such configuration parameter ... for process mysqld. (Bug #18127968) You can also find more information on the contents of this release in the change log: http://dev.mysql.com/doc/relnotes/mysql-cluster-manager/1.3/en/mcm
RE: MySQL Cluster or MySQL Cloud
Hi Neil, If you use MySQL Cluster then you have synchronous replication between the 2 data nodes which means that if one should fail you're guaranteed that the other contains the effects of every committed transaction and that the change has already been applied and so there is no delay while relay logs are applied before the automatic failover kicks in - which is why it can take less than a second. You also have a good scale-out story with MySQL Cluster as you can just continue to add more nodes (256 in total, 48 of which can be data nodes) withou having to worry about partitioning, failover etc. Regards, Andrew. -Original Message- From: Neil Tompkins [mailto:neil.tompk...@googlemail.com] Sent: 29 April 2013 14:50 To: Andrew Morgan Cc: [MySQL] Subject: Re: MySQL Cluster or MySQL Cloud Hi Andrew, Thanks for your response and the useful white paper. I've read the document in great detail. I'm looking for the best up time possible for my application and am still struggling to see the major differences with MySQL cluster compared to MySQL in the Cloud on multiple servers; apart from MySQL Cluster being much better solution for automatic failover including IP failover. Regards, Neil On Mon, Apr 29, 2013 at 8:47 AM, Andrew Morgan andrew.mor...@oracle.comwrote: Hi Neil, I hate just sending people off to white papers but you might get some good insights by taking a look at the MySQL Guide to High Availability Solutions paper - http://www.mysql.com/why-mysql/white-papers/mysql-guide-to-high- availa bility-solutions/ Regards, Andrew. Andrew Morgan - MySQL High Availability Product Management andrew.mor...@oracle.com @andrewmorgan www.clusterdb.com -Original Message- From: Neil Tompkins [mailto:neil.tompk...@googlemail.com] Sent: 27 April 2013 23:28 To: [MySQL] Subject: Fwd: MySQL Cluster or MySQL Cloud If deploying MySQL in the Cloud with two MySQL servers with master to master replication i have a good failover solution. Whats the different in terms of availability if we opted for MySQL Cluster instead ? -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
RE: MySQL Cluster or MySQL Cloud
See also Percona XtraDB Cluster. Will you nodes be in the same physical location? If so, what about floods, earthquakes, etc? Clouds are ephemeral; data wants to persist -Original Message- From: Andrew Morgan [mailto:andrew.mor...@oracle.com] Sent: Tuesday, April 30, 2013 12:36 AM To: Neil Tompkins Cc: [MySQL] Subject: RE: MySQL Cluster or MySQL Cloud Hi Neil, If you use MySQL Cluster then you have synchronous replication between the 2 data nodes which means that if one should fail you're guaranteed that the other contains the effects of every committed transaction and that the change has already been applied and so there is no delay while relay logs are applied before the automatic failover kicks in - which is why it can take less than a second. You also have a good scale-out story with MySQL Cluster as you can just continue to add more nodes (256 in total, 48 of which can be data nodes) withou having to worry about partitioning, failover etc. Regards, Andrew. -Original Message- From: Neil Tompkins [mailto:neil.tompk...@googlemail.com] Sent: 29 April 2013 14:50 To: Andrew Morgan Cc: [MySQL] Subject: Re: MySQL Cluster or MySQL Cloud Hi Andrew, Thanks for your response and the useful white paper. I've read the document in great detail. I'm looking for the best up time possible for my application and am still struggling to see the major differences with MySQL cluster compared to MySQL in the Cloud on multiple servers; apart from MySQL Cluster being much better solution for automatic failover including IP failover. Regards, Neil On Mon, Apr 29, 2013 at 8:47 AM, Andrew Morgan andrew.mor...@oracle.comwrote: Hi Neil, I hate just sending people off to white papers but you might get some good insights by taking a look at the MySQL Guide to High Availability Solutions paper - http://www.mysql.com/why-mysql/white-papers/mysql-guide-to-high- availa bility-solutions/ Regards, Andrew. Andrew Morgan - MySQL High Availability Product Management andrew.mor...@oracle.com @andrewmorgan www.clusterdb.com -Original Message- From: Neil Tompkins [mailto:neil.tompk...@googlemail.com] Sent: 27 April 2013 23:28 To: [MySQL] Subject: Fwd: MySQL Cluster or MySQL Cloud If deploying MySQL in the Cloud with two MySQL servers with master to master replication i have a good failover solution. Whats the different in terms of availability if we opted for MySQL Cluster instead ? -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
RE: MySQL Cluster or MySQL Cloud
Hi Neil, I hate just sending people off to white papers but you might get some good insights by taking a look at the MySQL Guide to High Availability Solutions paper - http://www.mysql.com/why-mysql/white-papers/mysql-guide-to-high-availability-solutions/ Regards, Andrew. Andrew Morgan - MySQL High Availability Product Management andrew.mor...@oracle.com @andrewmorgan www.clusterdb.com -Original Message- From: Neil Tompkins [mailto:neil.tompk...@googlemail.com] Sent: 27 April 2013 23:28 To: [MySQL] Subject: Fwd: MySQL Cluster or MySQL Cloud If deploying MySQL in the Cloud with two MySQL servers with master to master replication i have a good failover solution. Whats the different in terms of availability if we opted for MySQL Cluster instead ? -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: MySQL Cluster or MySQL Cloud
Hi Andrew, Thanks for your response and the useful white paper. I've read the document in great detail. I'm looking for the best up time possible for my application and am still struggling to see the major differences with MySQL cluster compared to MySQL in the Cloud on multiple servers; apart from MySQL Cluster being much better solution for automatic failover including IP failover. Regards, Neil On Mon, Apr 29, 2013 at 8:47 AM, Andrew Morgan andrew.mor...@oracle.comwrote: Hi Neil, I hate just sending people off to white papers but you might get some good insights by taking a look at the MySQL Guide to High Availability Solutions paper - http://www.mysql.com/why-mysql/white-papers/mysql-guide-to-high-availability-solutions/ Regards, Andrew. Andrew Morgan - MySQL High Availability Product Management andrew.mor...@oracle.com @andrewmorgan www.clusterdb.com -Original Message- From: Neil Tompkins [mailto:neil.tompk...@googlemail.com] Sent: 27 April 2013 23:28 To: [MySQL] Subject: Fwd: MySQL Cluster or MySQL Cloud If deploying MySQL in the Cloud with two MySQL servers with master to master replication i have a good failover solution. Whats the different in terms of availability if we opted for MySQL Cluster instead ? -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
RE: Mysql Cluster Sync-UP
Hi Kevin, What do you mean by running MySQL in cluster mode - MySQL Cluster? If so then the data is stored in the data nodes rather than the MySQL Servers and so if bad data is written to one MySQL Server then that same bad data will be viewed through the other MySQL Server too. Regards, Andrew. -Original Message- From: Kevin Peterson [mailto:qh.res...@gmail.com] Sent: 09 April 2013 04:58 To: mysql@lists.mysql.com Subject: Mysql Cluster Sync-UP Hi, I am running My-SQL in cluster mode with two machine. Want to know if mysql database get corrupted on one of the machine will it force the corruption on the other machine too or in this case sync between two mysql instances will stop after the corruption. Thanks, Kevin Peterson -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
RE: Converting Mysql to mysql cluster
-Original Message- From: Kevin Peterson [mailto:qh.res...@gmail.com] Sent: 27 March 2013 06:58 To: mysql@lists.mysql.com Subject: Converting Mysql to mysql cluster Hi, My site is using mysql and PHP, now for the scale purpose want to introduce mysql-cluster. Few questions are - 1. Do I need to change any code which is written in PHP. The answer is yes and no. There's a good chance that your application will work fine with MySQL Cluster without any changes *but* there are a few gotchas such as: - the current GA version of MySQL Cluster (7.2) doesn't implement Foreign Keys (coming in Cluster 7.3) - (ignoring BLOBs) rows cannot be larger than 13 Kb - no geo-spatial indexes - no full-text search A good place to get more information is http://www.mysql.com/why-mysql/white-papers/mysql-cluster-evaluation-guide/ . That guide also gives you some advice on scenarios where you *shouldn't* use MySQL Cluster. In addition, as you should expect, to get the best performance out of MySQL Cluster you may want to tweak your schema and/or application - you can get lots of tips from http://www.mysql.com/why-mysql/white-papers/guide-to-optimizing-performance-of-the-mysql-cluster/ 2. What are the steps to convert mysql to mysql-cluster. Basically, you need to backup your database (mysqldump), load it into a MySQL Server that's part of your Cluster (use http://www.clusterdb.com/mysql-cluster/auto-installer-labs-release/) to get your first Cluster up and running and then issue ALTER TABLE tab-name ENGINE=ndb; Appreciate the help. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
RE: mysql cluster and auto shard
-Original Message- From: Mike Franon [mailto:kongfra...@gmail.com] Sent: 18 March 2013 13:34 To: mysql@lists.mysql.com Subject: mysql cluster and auto shard I am looking at the best way to scale writes. Either using sharding with our existing infrastructure, or moving to mysql cluster. Does anyone have any pros/cons to using mysql cluster? I am trying to find a much better understanding on how the auto sharding works? Is it true we do not need to change code much on application level? As a starting point, I think it's worth taking a look at this white paper... http://www.mysql.com/why-mysql/white-papers/mysql-cluster-evaluation-guide/ Most things will continue to work when migrating to MySQL Cluster but of course (as with any storage engine) to get the best performance you'll probably need to make some changes; this second paper explains how to optimize for MySQL Cluster - hopefully that will give a good feeling for the types of changes that you might need/want to make... http://www.mysql.com/why-mysql/white-papers/guide-to-optimizing-performance-of-the-mysql-cluster/ Thanks -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
RE: mysql cluster and auto shard
Clustrix now has a software version of their auto-sharding system. (It used to be that they only sold an 'appliance'.) -Original Message- From: Andrew Morgan [mailto:andrew.mor...@oracle.com] Sent: Monday, March 18, 2013 6:51 AM To: Mike Franon Cc: mysql@lists.mysql.com Subject: RE: mysql cluster and auto shard -Original Message- From: Mike Franon [mailto:kongfra...@gmail.com] Sent: 18 March 2013 13:34 To: mysql@lists.mysql.com Subject: mysql cluster and auto shard I am looking at the best way to scale writes. Either using sharding with our existing infrastructure, or moving to mysql cluster. Does anyone have any pros/cons to using mysql cluster? I am trying to find a much better understanding on how the auto sharding works? Is it true we do not need to change code much on application level? As a starting point, I think it's worth taking a look at this white paper... http://www.mysql.com/why-mysql/white-papers/mysql-cluster- evaluation-guide/ Most things will continue to work when migrating to MySQL Cluster but of course (as with any storage engine) to get the best performance you'll probably need to make some changes; this second paper explains how to optimize for MySQL Cluster - hopefully that will give a good feeling for the types of changes that you might need/want to make... http://www.mysql.com/why-mysql/white-papers/guide-to-optimizing- performance-of-the-mysql-cluster/ Thanks -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Cluster Solution
Hi, I've used in the past MySQL Community Server 5.x. Everything is fine, however I'm now wanting to implement a new High Availability solution and am considering MySQL Cluster. However, I heard that MySQL Cluster doesn't support store procedures ? Are there any other restrictions I need to be aware of. Thanks Neil
RE: MySQL Cluster Solution
Hi Neil, MySQL Cluster *does* support stored procedures. There are some limitation that MySQL Cluster has; this white paper would be a good place to start... http://www.mysql.com/why-mysql/white-papers/mysql-cluster-evaluation-guide/ Regards, Andrew. -Original Message- From: Neil Tompkins [mailto:neil.tompk...@googlemail.com] Sent: 07 March 2013 14:57 To: [MySQL] Subject: MySQL Cluster Solution Hi, I've used in the past MySQL Community Server 5.x. Everything is fine, however I'm now wanting to implement a new High Availability solution and am considering MySQL Cluster. However, I heard that MySQL Cluster doesn't support store procedures ? Are there any other restrictions I need to be aware of. Thanks Neil -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: MySQL Cluster Solution
- Original Message - From: Neil Tompkins neil.tompk...@googlemail.com Subject: MySQL Cluster Solution I've used in the past MySQL Community Server 5.x. Everything is fine, however I'm now wanting to implement a new High Availability solution and am considering MySQL Cluster. However, I heard that MySQL Cluster doesn't support store procedures ? Are there any other restrictions I need to be aware of. It is a completely different product, Neil, which just happens to also have a gateway for MySQL. It is not 'just another storage engine' - study it hard, and do extensive testing before you even consider switching. That is not to say that it might not be a good match for your needs; just that it's not a quick switch. -- Unhappiness is discouraged and will be corrected with kitten pictures. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
RE: MySQL Cluster Solution
What do _you_ mean by a new High Availability solution? See also Percona Cluster. It uses InnoDB (XtraDB), so that might be zero change for you. Oops, except that you should check for errors after COMMIT. -Original Message- From: Johan De Meersman [mailto:vegiv...@tuxera.be] Sent: Thursday, March 07, 2013 7:06 AM To: Neil Tompkins Cc: [MySQL] Subject: Re: MySQL Cluster Solution - Original Message - From: Neil Tompkins neil.tompk...@googlemail.com Subject: MySQL Cluster Solution I've used in the past MySQL Community Server 5.x. Everything is fine, however I'm now wanting to implement a new High Availability solution and am considering MySQL Cluster. However, I heard that MySQL Cluster doesn't support store procedures ? Are there any other restrictions I need to be aware of. It is a completely different product, Neil, which just happens to also have a gateway for MySQL. It is not 'just another storage engine' - study it hard, and do extensive testing before you even consider switching. That is not to say that it might not be a good match for your needs; just that it's not a quick switch. -- Unhappiness is discouraged and will be corrected with kitten pictures. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: MySQL Cluster alerts
Hi Bheemsen, looks like a few different things going on there; if you have a MySQL support contract/subscription then it would be worth raising SRs - it doesn't need to be a bug, it's fine tyo ask questions too. A couple of things that spring to mind in-line I am frequently seeing the following alerts in our production MySQL Cluster environment. Do you have any metrics, guidelines and scripts to monitor and fix these alerts? Any help is appreciated. Temporary Tables To Disk Ratio Excessive Excessive Disk Temporary Table Usage Detected Table Scans Excessive Indexes Not Being Used Efficiently If you're using MySQL Cluster 7.2 then you should run OPTIMIZE TABLE for each of your tables (repeat that step whenever you make schemas changes to it, add an index or make very signifficant data changes). This will make the optimizer make better use of available indexes. Use the query analyzer in MySQL Enterprise Monitor (MEM) to see which queries are taking the time as these are likely to be the table scans (full table scans should be avoided as much as possible). You can use the EXPLAIN command to see if individual queries are making use of the available indexes. Try adding new indexes if they're missing for high-running transactions. Thread Cache Size May Not Be Optimal Cluster DiskPageBuffer Hit Ratio Is Low Note that you might observe this after restarting a data node as the cache must be repopulated as queries come in. If you're seeing this at other times or the MEM graphs show that the DiskPageBuffer Hit Ratio is consistently low then consider increasing it... http://dev.mysql.com/doc/mysql-cluster-excerpt/5.1/en/mysql-cluster-ndbd-definition.html#ndbparam-ndbd-diskpagebuffermemory -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Cluster alerts
Hi list I am frequently seeing the following alerts in our production MySQL Cluster environment. Does anyone have any metrics, guidelines and scripts to monitor and fix these alerts? Any help is appreciated. Temporary Tables To Disk Ratio Excessive Excessive Disk Temporary Table Usage Detected Table Scans Excessive Indexes Not Being Used Efficiently Thread Cache Size May Not Be Optimal Cluster DiskPageBuffer Hit Ratio Is Low -- *Thanks* *BA*
Backup Error while backing up MySQL Cluster
Hi, After following the steps at the following website, I tried to do an online backup of the cluster. http://dev.mysql.com/doc/refman/5.0/en/mysql-cluster-backup-using-management-client.html It is a plain vanilla command which is below. The cluster is almost an empty database, but backup is crashing at least one data node and was never successful. ndb_mgm -e START BACKUP WAIT COMPLETED Did anyone have this kind of error before? I tried searching on web but could not find a solution. Here is the error I received. Connected to Management Server at: localhost:1186 Waiting for completed, this may take several minutes Backup failed * 3001: Could not start backup *Backup aborted due to node failure: Permanent error: Internal error ALERT-- Node 2: Backup 2 started from 49 has been aborted. Error: 1326 Here is little background about our setup. OS: Redhat Linux 5.8 Cluster: MySQL 5.5, NDB 7.2.7 Cluster was installed and set up on two hosts using MCM, one host hosting mysqld, ndb_mgmd and the other hosting ndbmtd1 and ndbmtd2. I even tried by setting up the following parameters, but got the same error again. set BackupDataBufferSize:ndbmtd=256M attcluster; set BackupLogBufferSize:ndbmtd=256M attcluster; set BackupMemory:ndbmtd=512M attcluster; set BackupWriteSize:ndbmtd=32M attcluster; set BackupMaxWriteSize:ndbmtd=128M attcluster; Here are some links I found on web similar to my error. http://forums.mysql.com/read.php?25,230891,230959#msg-230959 http://grokbase.com/t/mysql/cluster/0578z8cj71/backup-error http://bugs.mysql.com/bug.php?id=66104 mcm show status -r attcluster; ++--+-+-+---+-+ | NodeId | Process | Host| Status | Nodegroup | Package | ++--+-+-+---+-+ | 49 | ndb_mgmd | ut06sandboxdb01 | running | | 7.2.7 | | 50 | mysqld | ut06sandboxdb01 | running | | 7.2.7 | | 1 | ndbmtd | ut06sandboxdb02 | failed | 0 | 7.2.7 | | 2 | ndbmtd | ut06sandboxdb02 | running | 0 | 7.2.7 | ++--+-+-+---+-+ 4 rows in set (0.07 sec) mcm I see the core dump in DataDir of node 1. [root@ut06sandboxdb02 data]# ls -ltr /opt/app/mcm-1.1.6_64-linux-rhel5-x86/mcm_data/clusters/attcluster/1/data total 16949760 -rw-rw-r-- 1 mysql mysql 0 Oct 19 12:23 ndb_1_out.err -rw-rw-r-- 1 mysql mysql 1 Oct 21 04:02 ndb_1_trace.log.next -rw-rw-r-- 1 mysql mysql568 Oct 21 04:02 ndb_1_error.log -rw-rw-r-- 1 mysql mysql 12202 Oct 21 04:02 ndb_1_trace.log.1_t4 -rw-rw-r-- 1 mysql mysql 923467 Oct 21 04:02 ndb_1_trace.log.1_t3 -rw-rw-r-- 1 mysql mysql 923489 Oct 21 04:02 ndb_1_trace.log.1_t2 -rw-rw-r-- 1 mysql mysql 934663 Oct 21 04:02 ndb_1_trace.log.1_t1 -rw-rw-r-- 1 mysql mysql 948989 Oct 21 04:02 ndb_1_trace.log.1 -rw--- 1 mysql mysql 4104044544 Oct 23 11:04 core.21529 -rw--- 1 mysql mysql 5880332288 Oct 23 18:22 core.8108 -rw--- 1 mysql mysql 4538155008 Oct 23 23:56 core.1124 -rw--- 1 mysql mysql 2924789760 Oct 24 00:32 core.9176 -rw-rw-r-- 1 mysql mysql 460826 Oct 24 00:33 ndb_1_out.log Here is more info from mcmd.log. I really appreciate any help on this. 2012-10-23 18:09:58.193: (message) [T0x19add970 RECFG]: [1,ndb_mgmd,0]: 2012-10-23 18:09:58 [MgmtSrvr] WARNING -- Node 2: Failed to memlock pages, error: 12 (Cannot allocate memory) [1,ndb_mgmd,0]: 2012-10-23 18:09:58 [MgmtSrvr] INFO -- Node 2: Waiting 30 sec for nodes 1 to connect, nodes [ all: 1 and 2 connected: 2 no-wait: ] 2012-10-23 18:09:58.193: (message) [T0x19add970 RECFG]: [1,ndb_mgmd,0]: 2012-10-23 18:09:58 [MgmtSrvr] INFO -- Node 2: Waiting 30 sec for nodes 1 to connect, nodes [ all: 1 and 2 connected: 2 no-wait: ] 2012-10-23 18:09:58.286: (message) [T0x19add970 RECFG]: [1,ndb_mgmd,0]: 2012-10-23 18:09:58 [MgmtSrvr] INFO -- Node 2: Communication to Node 1 opened [1,ndb_mgmd,0]: 2012-10-23 18:09:58 [MgmtSrvr] INFO -- Node 2: Node 1 Connected 2012-10-23 18:09:58.347: (message) last message repeated 1 times 2012-10-23 18:09:58.347: (message) [T0x19add970 RECFG]: [1,ndb_mgmd,0]: 2012-10-23 18:09:58 [MgmtSrvr] INFO -- Node 1: Node 2 Connected [1,ndb_mgmd,0]: 2012-10-23 18:09:58 [MgmtSrvr] INFO -- Node 1: Node 2: API mysql-5.5.25 ndb-7.2.7 [1,ndb_mgmd,0]: 2012-10-23 18:09:58 [MgmtSrvr] INFO -- Node 2: CM_REGCONF president = 1, own Node = 2, our dynamic id = 0/13 [1,ndb_mgmd,0]: 2012-10-23 18:09:58 [MgmtSrvr] INFO -- Node 2: Node 1: API mysql-5.5.25 ndb-7.2.7 [1,ndb_mgmd,0]: 2012-10-23 18:09:58 [MgmtSrvr] INFO -- Node 2: Start phase 1 completed 2012-10-23 18:09:58.437: (message) last message repeated 1 times 2012-10-23 18:09:58.437: (message) [T0x19add970 RECFG]: [1,ndb_mgmd,0]: 2012-10-23 18:09:58 [MgmtSrvr] INFO -- Node 2: Start phase 2 completed (node restart) 2012-10-23 18:09:58.467: (message
Re: Backup Error while backing up MySQL Cluster
On 10/24/2012 11:57 AM, Bheemsen Aitha wrote: Hi, After following the steps at the following website, I tried to do an online backup of the cluster. http://dev.mysql.com/doc/refman/5.0/en/mysql-cluster-backup-using-management-client.html It is a plain vanilla command which is below. The cluster is almost an empty database, but backup is crashing at least one data node and was never successful. ndb_mgm -e START BACKUP WAIT COMPLETED Did anyone have this kind of error before? I tried searching on web but could not find a solution. Here is the error I received. Connected to Management Server at: localhost:1186 Waiting for completed, this may take several minutes Backup failed * 3001: Could not start backup *Backup aborted due to node failure: Permanent error: Internal error ALERT-- Node 2: Backup 2 started from 49 has been aborted. Error: 1326 Here is little background about our setup. OS: Redhat Linux 5.8 Cluster: MySQL 5.5, NDB 7.2.7 Cluster was installed and set up on two hosts using MCM, one host hosting mysqld, ndb_mgmd and the other hosting ndbmtd1 and ndbmtd2. I even tried by setting up the following parameters, but got the same error again. set BackupDataBufferSize:ndbmtd=256M attcluster; set BackupLogBufferSize:ndbmtd=256M attcluster; set BackupMemory:ndbmtd=512M attcluster; set BackupWriteSize:ndbmtd=32M attcluster; set BackupMaxWriteSize:ndbmtd=128M attcluster; Here are some links I found on web similar to my error. http://forums.mysql.com/read.php?25,230891,230959#msg-230959 http://grokbase.com/t/mysql/cluster/0578z8cj71/backup-error http://bugs.mysql.com/bug.php?id=66104 At the bottom of the bug you found, it says: [7 Sep 6:31] Ole John Aske This bug has been fixed in MySQL CLuster 7.2.8 which is now available on http://dev.mysql.com/downloads/cluster/ You need to upgrade to receive this fix. Let us know if that works. -- Shawn Green MySQL Principal Technical Support Engineer Oracle USA, Inc. - Hardware and Software, Engineered to Work Together. Office: Blountville, TN -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: Backup Error while backing up MySQL Cluster
Just for others to know, it was the memory problem. I re-set the memory parameters for ndbmtd (two nodes) to minimum. Then I could run the backup successfully. Thanks BA On Wed, Oct 24, 2012 at 11:57 AM, Bheemsen Aitha pgb...@motorola.comwrote: Hi, After following the steps at the following website, I tried to do an online backup of the cluster. http://dev.mysql.com/doc/refman/5.0/en/mysql-cluster-backup-using-management-client.html It is a plain vanilla command which is below. The cluster is almost an empty database, but backup is crashing at least one data node and was never successful. ndb_mgm -e START BACKUP WAIT COMPLETED Did anyone have this kind of error before? I tried searching on web but could not find a solution. Here is the error I received. Connected to Management Server at: localhost:1186 Waiting for completed, this may take several minutes Backup failed * 3001: Could not start backup *Backup aborted due to node failure: Permanent error: Internal error ALERT-- Node 2: Backup 2 started from 49 has been aborted. Error: 1326 Here is little background about our setup. OS: Redhat Linux 5.8 Cluster: MySQL 5.5, NDB 7.2.7 Cluster was installed and set up on two hosts using MCM, one host hosting mysqld, ndb_mgmd and the other hosting ndbmtd1 and ndbmtd2. I even tried by setting up the following parameters, but got the same error again. set BackupDataBufferSize:ndbmtd=256M attcluster; set BackupLogBufferSize:ndbmtd=256M attcluster; set BackupMemory:ndbmtd=512M attcluster; set BackupWriteSize:ndbmtd=32M attcluster; set BackupMaxWriteSize:ndbmtd=128M attcluster; Here are some links I found on web similar to my error. http://forums.mysql.com/read.php?25,230891,230959#msg-230959 http://grokbase.com/t/mysql/cluster/0578z8cj71/backup-error http://bugs.mysql.com/bug.php?id=66104 mcm show status -r attcluster; ++--+-+-+---+-+ | NodeId | Process | Host| Status | Nodegroup | Package | ++--+-+-+---+-+ | 49 | ndb_mgmd | ut06sandboxdb01 | running | | 7.2.7 | | 50 | mysqld | ut06sandboxdb01 | running | | 7.2.7 | | 1 | ndbmtd | ut06sandboxdb02 | failed | 0 | 7.2.7 | | 2 | ndbmtd | ut06sandboxdb02 | running | 0 | 7.2.7 | ++--+-+-+---+-+ 4 rows in set (0.07 sec) mcm I see the core dump in DataDir of node 1. [root@ut06sandboxdb02 data]# ls -ltr /opt/app/mcm-1.1.6_64-linux-rhel5-x86/mcm_data/clusters/attcluster/1/data total 16949760 -rw-rw-r-- 1 mysql mysql 0 Oct 19 12:23 ndb_1_out.err -rw-rw-r-- 1 mysql mysql 1 Oct 21 04:02 ndb_1_trace.log.next -rw-rw-r-- 1 mysql mysql568 Oct 21 04:02 ndb_1_error.log -rw-rw-r-- 1 mysql mysql 12202 Oct 21 04:02 ndb_1_trace.log.1_t4 -rw-rw-r-- 1 mysql mysql 923467 Oct 21 04:02 ndb_1_trace.log.1_t3 -rw-rw-r-- 1 mysql mysql 923489 Oct 21 04:02 ndb_1_trace.log.1_t2 -rw-rw-r-- 1 mysql mysql 934663 Oct 21 04:02 ndb_1_trace.log.1_t1 -rw-rw-r-- 1 mysql mysql 948989 Oct 21 04:02 ndb_1_trace.log.1 -rw--- 1 mysql mysql 4104044544 Oct 23 11:04 core.21529 -rw--- 1 mysql mysql 5880332288 Oct 23 18:22 core.8108 -rw--- 1 mysql mysql 4538155008 Oct 23 23:56 core.1124 -rw--- 1 mysql mysql 2924789760 Oct 24 00:32 core.9176 -rw-rw-r-- 1 mysql mysql 460826 Oct 24 00:33 ndb_1_out.log Here is more info from mcmd.log. I really appreciate any help on this. 2012-10-23 18:09:58.193: (message) [T0x19add970 RECFG]: [1,ndb_mgmd,0]: 2012-10-23 18:09:58 [MgmtSrvr] WARNING -- Node 2: Failed to memlock pages, error: 12 (Cannot allocate memory) [1,ndb_mgmd,0]: 2012-10-23 18:09:58 [MgmtSrvr] INFO -- Node 2: Waiting 30 sec for nodes 1 to connect, nodes [ all: 1 and 2 connected: 2 no-wait: ] 2012-10-23 18:09:58.193: (message) [T0x19add970 RECFG]: [1,ndb_mgmd,0]: 2012-10-23 18:09:58 [MgmtSrvr] INFO -- Node 2: Waiting 30 sec for nodes 1 to connect, nodes [ all: 1 and 2 connected: 2 no-wait: ] 2012-10-23 18:09:58.286: (message) [T0x19add970 RECFG]: [1,ndb_mgmd,0]: 2012-10-23 18:09:58 [MgmtSrvr] INFO -- Node 2: Communication to Node 1 opened [1,ndb_mgmd,0]: 2012-10-23 18:09:58 [MgmtSrvr] INFO -- Node 2: Node 1 Connected 2012-10-23 18:09:58.347: (message) last message repeated 1 times 2012-10-23 18:09:58.347: (message) [T0x19add970 RECFG]: [1,ndb_mgmd,0]: 2012-10-23 18:09:58 [MgmtSrvr] INFO -- Node 1: Node 2 Connected [1,ndb_mgmd,0]: 2012-10-23 18:09:58 [MgmtSrvr] INFO -- Node 1: Node 2: API mysql-5.5.25 ndb-7.2.7 [1,ndb_mgmd,0]: 2012-10-23 18:09:58 [MgmtSrvr] INFO -- Node 2: CM_REGCONF president = 1, own Node = 2, our dynamic id = 0/13 [1,ndb_mgmd,0]: 2012-10-23 18:09:58 [MgmtSrvr] INFO -- Node 2: Node 1: API mysql-5.5.25 ndb-7.2.7 [1,ndb_mgmd,0
Re: Mysql cluster installation error
Hi Aastha, I'm not 100% sure but you could try defining the full connectstring using: ndb-connectstring = localhost:1186 See if that helps. Regards, From: Aastha aast...@gmail.com To: mysql@lists.mysql.com Sent: Sunday, September 23, 2012 7:51 AM Subject: Mysql cluster installation error Hello, I am trying to install MySQL cluster on three physical machines. Management Node on one machine. Data Node on two machines. SQL node on the same machine as Management Node. Management node started Data Nodes started *SQL node started but not connected to Management NOde and it gives no error * C:\mysql\binndb_mgm -e show Connected to Management Server at: localhost:1186 Cluster Configuration - [ndbd(NDB)] 2 node(s) id=8 @172.16.56.8 (mysql-5.5.25 ndb-7.2.7, Nodegroup: 0, Master) id=9 @172.16.56.9 (mysql-5.5.25 ndb-7.2.7, Nodegroup: 0) [ndb_mgmd(MGM)] 1 node(s) id=6 @172.16.56.7 (mysql-5.5.25 ndb-7.2.7) [mysqld(API)] 1 node(s) id=7 (not connected, accepting connect from 172.16.56.7) *config.ini* [ndbd default] # Options affecting ndbd processes on all data nodes: NoOfReplicas=2 # Number of replicas DataDir=C:/mysql/bin/cluster-data # Directory for each data node's data files DataMemory=80M # Memory allocated to data storage IndexMemory=18M # Memory allocated to index storage [ndb_mgmd] # Management process options: HostName=172.16.56.7 # Hostname or IP address of management node DataDir=C:/mysql/bin/cluster-logs # Directory for management node log files NodeId=5 [ndbd] # Options for data node A: HostName=172.16.56.8 # Hostname or IP address NodeId=8 MaxNoOfOrderedIndexes=1024 MaxNoOfAttributes=3000 # added 2012.8.08 [ndbd] # Options for data node B: HostName=172.16.56.9 # Hostname or IP address NodeId=9 MaxNoOfOrderedIndexes=1024 MaxNoOfAttributes=3000 # added 2012.8.08 [mysqld] # SQL node options: HostName=172.16.56.7 # Hostname or IP address NodeId=7 *my.ini* * * [mysql_cluster] # Options for management node process config-file=c:/mysql/bin/config.ini configdir=c:/mysql/bin/cluster-cache/ [mysqld] # Options for mysqld process: ndbcluster # run NDB storage engine ndb-connectstring=172.16.56.7 # location of management server ndb-nodeid=7 server-id=7 default-storage-engine=ndbcluster Could anyone help to identify/ Aastha Gupta
Re: Mysql cluster installation error
Thanks Nitin. I specied the location of my.ini while starting the SQL node and it worked fine. I have anothe rquestion : How to connect the cluster and reomte host. And i have to copy a schema from one Mysql clsuter to another. How do i do that. Regards, On Sun, Sep 23, 2012 at 3:13 AM, Nitin Mehta ntn...@yahoo.com wrote: Hi Aastha, I'm not 100% sure but you could try defining the full connectstring using: ndb-connectstring = localhost:1186 See if that helps. Regards, From: Aastha aast...@gmail.com To: mysql@lists.mysql.com Sent: Sunday, September 23, 2012 7:51 AM Subject: Mysql cluster installation error Hello, I am trying to install MySQL cluster on three physical machines. Management Node on one machine. Data Node on two machines. SQL node on the same machine as Management Node. Management node started Data Nodes started *SQL node started but not connected to Management NOde and it gives no error * C:\mysql\binndb_mgm -e show Connected to Management Server at: localhost:1186 Cluster Configuration - [ndbd(NDB)] 2 node(s) id=8@172.16.56.8 (mysql-5.5.25 ndb-7.2.7, Nodegroup: 0, Master) id=9@172.16.56.9 (mysql-5.5.25 ndb-7.2.7, Nodegroup: 0) [ndb_mgmd(MGM)] 1 node(s) id=6@172.16.56.7 (mysql-5.5.25 ndb-7.2.7) [mysqld(API)] 1 node(s) id=7 (not connected, accepting connect from 172.16.56.7) *config.ini* [ndbd default] # Options affecting ndbd processes on all data nodes: NoOfReplicas=2# Number of replicas DataDir=C:/mysql/bin/cluster-data # Directory for each data node's data files DataMemory=80M# Memory allocated to data storage IndexMemory=18M # Memory allocated to index storage [ndb_mgmd] # Management process options: HostName=172.16.56.7# Hostname or IP address of management node DataDir=C:/mysql/bin/cluster-logs # Directory for management node log files NodeId=5 [ndbd] # Options for data node A: HostName=172.16.56.8 # Hostname or IP address NodeId=8 MaxNoOfOrderedIndexes=1024 MaxNoOfAttributes=3000 # added 2012.8.08 [ndbd] # Options for data node B: HostName=172.16.56.9 # Hostname or IP address NodeId=9 MaxNoOfOrderedIndexes=1024 MaxNoOfAttributes=3000 # added 2012.8.08 [mysqld] # SQL node options: HostName=172.16.56.7 # Hostname or IP address NodeId=7 *my.ini* * * [mysql_cluster] # Options for management node process config-file=c:/mysql/bin/config.ini configdir=c:/mysql/bin/cluster-cache/ [mysqld] # Options for mysqld process: ndbcluster # run NDB storage engine ndb-connectstring=172.16.56.7 # location of management server ndb-nodeid=7 server-id=7 default-storage-engine=ndbcluster Could anyone help to identify/ Aastha Gupta
Re: Mysql cluster installation error
If all you need to transfer is schema, do it the same way you would any other table type: use mysqldump with the - - no-data option. On 2012-09-23 1:29 PM, Aastha aast...@gmail.com wrote: Thanks Nitin. I specied the location of my.ini while starting the SQL node and it worked fine. I have anothe rquestion : How to connect the cluster and reomte host. And i have to copy a schema from one Mysql clsuter to another. How do i do that. Regards, On Sun, Sep 23, 2012 at 3:13 AM, Nitin Mehta ntn...@yahoo.com wrote: Hi Aastha, I'm not 10...
Re: Mysql cluster installation error
Thanks! And how do i connect the cluster from the remote host. When i try to connect one of the SQL node through remote host it says access denied. WHile the same is working fine from local host. Kindly help. Thanks! On Sun, Sep 23, 2012 at 12:35 PM, Michael Dykman mdyk...@gmail.com wrote: If all you need to transfer is schema, do it the same way you would any other table type: use mysqldump with the - - no-data option. On 2012-09-23 1:29 PM, Aastha aast...@gmail.com wrote: Thanks Nitin. I specied the location of my.ini while starting the SQL node and it worked fine. I have anothe rquestion : How to connect the cluster and reomte host. And i have to copy a schema from one Mysql clsuter to another. How do i do that. Regards, On Sun, Sep 23, 2012 at 3:13 AM, Nitin Mehta ntn...@yahoo.com wrote: Hi Aastha, I'm not 10...
Re: Mysql cluster installation error
If your remote host is not configured as a sql node to your cluster, you don't need to just to import the schema. Run mysqldump on any client machine specifying any of your configured sql nodes via -host=. On 2012-09-23 1:40 PM, Aastha aast...@gmail.com wrote: Thanks! And how do i connect the cluster from the remote host. When i try to connect one of the SQL node through remote host it says access denied. WHile the same is working fine from local host. Kindly help. Thanks! On Sun, Sep 23, 2012 at 12:35 PM, Michael Dykman mdyk...@gmail.com wrote: If all you need to ...
RE: Mysql cluster installation error
CONTACT the server admin and request access to the MySQL Instance located there Martin __ Verzicht und Vertraulichkeitanmerkung Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Date: Sun, 23 Sep 2012 12:40:17 -0500 Subject: Re: Mysql cluster installation error From: aast...@gmail.com To: mdyk...@gmail.com CC: mysql@lists.mysql.com Thanks! And how do i connect the cluster from the remote host. When i try to connect one of the SQL node through remote host it says access denied. WHile the same is working fine from local host. Kindly help. Thanks! On Sun, Sep 23, 2012 at 12:35 PM, Michael Dykman mdyk...@gmail.com wrote: If all you need to transfer is schema, do it the same way you would any other table type: use mysqldump with the - - no-data option. On 2012-09-23 1:29 PM, Aastha aast...@gmail.com wrote: Thanks Nitin. I specied the location of my.ini while starting the SQL node and it worked fine. I have anothe rquestion : How to connect the cluster and reomte host. And i have to copy a schema from one Mysql clsuter to another. How do i do that. Regards, On Sun, Sep 23, 2012 at 3:13 AM, Nitin Mehta ntn...@yahoo.com wrote: Hi Aastha, I'm not 10...
Mysql cluster installation error
Hello, I am trying to install MySQL cluster on three physical machines. Management Node on one machine. Data Node on two machines. SQL node on the same machine as Management Node. Management node started Data Nodes started *SQL node started but not connected to Management NOde and it gives no error * C:\mysql\binndb_mgm -e show Connected to Management Server at: localhost:1186 Cluster Configuration - [ndbd(NDB)] 2 node(s) id=8@172.16.56.8 (mysql-5.5.25 ndb-7.2.7, Nodegroup: 0, Master) id=9@172.16.56.9 (mysql-5.5.25 ndb-7.2.7, Nodegroup: 0) [ndb_mgmd(MGM)] 1 node(s) id=6@172.16.56.7 (mysql-5.5.25 ndb-7.2.7) [mysqld(API)] 1 node(s) id=7 (not connected, accepting connect from 172.16.56.7) *config.ini* [ndbd default] # Options affecting ndbd processes on all data nodes: NoOfReplicas=2# Number of replicas DataDir=C:/mysql/bin/cluster-data # Directory for each data node's data files DataMemory=80M# Memory allocated to data storage IndexMemory=18M # Memory allocated to index storage [ndb_mgmd] # Management process options: HostName=172.16.56.7# Hostname or IP address of management node DataDir=C:/mysql/bin/cluster-logs # Directory for management node log files NodeId=5 [ndbd] # Options for data node A: HostName=172.16.56.8 # Hostname or IP address NodeId=8 MaxNoOfOrderedIndexes=1024 MaxNoOfAttributes=3000 # added 2012.8.08 [ndbd] # Options for data node B: HostName=172.16.56.9 # Hostname or IP address NodeId=9 MaxNoOfOrderedIndexes=1024 MaxNoOfAttributes=3000 # added 2012.8.08 [mysqld] # SQL node options: HostName=172.16.56.7 # Hostname or IP address NodeId=7 *my.ini* * * [mysql_cluster] # Options for management node process config-file=c:/mysql/bin/config.ini configdir=c:/mysql/bin/cluster-cache/ [mysqld] # Options for mysqld process: ndbcluster # run NDB storage engine ndb-connectstring=172.16.56.7 # location of management server ndb-nodeid=7 server-id=7 default-storage-engine=ndbcluster Could anyone help to identify/ Aastha Gupta
Re: Myisam won't support replication in an MySQL Cluster environment
- Original Message - From: Charles Brown cbr...@bmi.com Interestingly, over the years, I've been reading your postings and threads - without a doubt you're a major contributor. You've been very resourceful and helpful to your peers. We may never know what caused you to violently snap this time. However, I would encourage Interestingly, if you *had* been following so closely over the years, you'd know both that this isn't violently snapping at all - I've seen him explode much worse; *and* that you should both provide relevant data as well as actually bother to read people's answers if you expect help. you to continue to be nice and respectful to others -- particularly others you don't know. While this forum provides an excellent opportunity for us to exchange and share our experiences in MySQL, yet we expect everyone to conduct themselves politely and restrain from ideological overtures. The thought that an intelligent individual like you would bring himself this low flies in the face of all rational behavior. That's a whole lot of quite good managementspeak - and just as meaningless. I've seen your threads over the past couple of weeks, and have come to the same conclusion as Harald: you keep reposting the same inane question, all the while blatantly ignoring any and all relevant and informative replies you get from knowledgeable and experienced DBAs, highly specialised consultants and people from the actualy MySQL support alike. The main difference between his and my reaction to the kind of behaviour you are showing is that he get annoyed, whereas I simply ignore the thread. The answer to your question has been posted repeatedly. There is also perfectly good documentation available, yet you choose to ignore both and keep reposting the same thing over and over again, giving no indication of any form of comprehension whatsoever. Go read the documentation, go search the internet, and if you *still* have issues, come back here and ask intelligent questions instead of things you find in the first few pages of any introductory paper. This list consists of volunteers who freely provide their expertise, spending their time and asking nothing in return. It is NOT your personal helpdesk. -- Bier met grenadyn Is als mosterd by den wyn Sy die't drinkt, is eene kwezel Hy die't drinkt, is ras een ezel -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: Myisam won't support replication in an MySQL Cluster environment
Am 04.05.2012 06:45, schrieb Brown: Does anyone have idea or experienced in MySQL Cluster configured for bi-directional replication. Please advise me if you have to use NDBcluster engine in order to get replication between the data nodes. I'm using MYISAM on several tables that will not replicate. whould you please start to read DOCUMENTATIONS instead open permanently new threads for the same problem which has the root cause that it seems you are doing a job without any qualification for it you can not expectz a mailing-list to replace documentation and education in your job - really this is not the intention of a mailinglist and yes, if you still do not know how to act after reading docs hire somebody who knows and pay him money signature.asc Description: OpenPGP digital signature
RE: Myisam won't support replication in an MySQL Cluster environment
Hello Mr Reindl, Interestingly, over the years, I've been reading your postings and threads - without a doubt you're a major contributor. You've been very resourceful and helpful to your peers. We may never know what caused you to violently snap this time. However, I would encourage you to continue to be nice and respectful to others -- particularly others you don't know. While this forum provides an excellent opportunity for us to exchange and share our experiences in MySQL, yet we expect everyone to conduct themselves politely and restrain from ideological overtures. The thought that an intelligent individual like you would bring himself this low flies in the face of all rational behavior. Best regards, -Original Message- From: Reindl Harald [mailto:h.rei...@thelounge.net] Sent: Friday, May 04, 2012 3:23 AM To: mysql@lists.mysql.com Subject: Re: Myisam won't support replication in an MySQL Cluster environment Am 04.05.2012 06:45, schrieb Brown: Does anyone have idea or experienced in MySQL Cluster configured for bi-directional replication. Please advise me if you have to use NDBcluster engine in order to get replication between the data nodes. I'm using MYISAM on several tables that will not replicate. whould you please start to read DOCUMENTATIONS instead open permanently new threads for the same problem which has the root cause that it seems you are doing a job without any qualification for it you can not expectz a mailing-list to replace documentation and education in your job - really this is not the intention of a mailinglist and yes, if you still do not know how to act after reading docs hire somebody who knows and pay him money This message is intended only for the use of the Addressee and may contain information that is PRIVILEGED and CONFIDENTIAL. If you are not the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please erase all copies of the message and its attachments and notify us immediately. Thank you.
Re: Myisam won't support replication in an MySQL Cluster environment
you did not get my point the problem is you are starting permanently NEW threads and you are not inclduing ANY informations in your posts I noticed that... as start is a bad joke you ahve to provide at least logs, configurations and describe HOW you notice things becasue others have no idea how your setup looks like BTW: get rid of your This message is intended only for the use of the Addressee at the bottom of your mails, this is only childish because a) after read the message nobody can erase the content from his brain and b) WHO is the Addressee if not the one you sent your mail? additionally get rid of HTML messages if you are posting to mailing-lists Am 04.05.2012 15:54, schrieb Brown: Hello Mr Reindl, Interestingly, over the years, I've been reading your postings and threads - without a doubt you're a major contributor. You've been very resourceful and helpful to your peers. We may never know what caused you to violently snap this time. However, I would encourage you to continue to be nice and respectful to others -- particularly others you don't know. While this forum provides an excellent opportunity for us to exchange and share our experiences in MySQL, yet we expect everyone to conduct themselves politely and restrain from ideological overtures. The thought that an intelligent individual like you would bring himself this low flies in the face of all rational behavior. Best regards, -Original Message- From: Reindl Harald [mailto:h.rei...@thelounge.net] Sent: Friday, May 04, 2012 3:23 AM To: mysql@lists.mysql.com Subject: Re: Myisam won't support replication in an MySQL Cluster environment Am 04.05.2012 06:45, schrieb Brown: Does anyone have idea or experienced in MySQL Cluster configured for bi-directional replication. Please advise me if you have to use NDBcluster engine in order to get replication between the data nodes. I'm using MYISAM on several tables that will not replicate. whould you please start to read DOCUMENTATIONS instead open permanently new threads for the same problem which has the root cause that it seems you are doing a job without any qualification for it you can not expectz a mailing-list to replace documentation and education in your job - really this is not the intention of a mailinglist and yes, if you still do not know how to act after reading docs hire somebody who knows and pay him money signature.asc Description: OpenPGP digital signature
Myisam won't support replication in an MySQL Cluster environment
Does anyone have idea or experienced in MySQL Cluster configured for bi-directional replication. Please advise me if you have to use NDBcluster engine in order to get replication between the data nodes. I'm using MYISAM on several tables that will not replicate. This message is intended only for the use of the Addressee and may contain information that is PRIVILEGED and CONFIDENTIAL. If you are not the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please erase all copies of the message and its attachments and notify us immediately. Thank you.
Myisam won't support replication in an MySQL Cluster environment
Does anyone have idea or experienced in MySQL Cluster configured for bi-directional replication. Please advise me if you have to use NDBcluster engine in order to get replication between the data nodes. I'm using MYISAM on several tables that will not replicate. This message is intended only for the use of the Addressee and may contain information that is PRIVILEGED and CONFIDENTIAL. If you are not the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please erase all copies of the message and its attachments and notify us immediately. Thank you.
mysql cluster with 3 db/data and 2 mgm nodes
Hi, i am about to configure mysql-cluster setup with 3 data+sql nodes and 2 mgm nodes, i would like to know if it's ok to go ahead with this setup, because somewhere i read it's preferred to setup _even_ number of data nodes instead e.g. 2, 4, or 6. please advice me. thanks and best regards, -m -- Ghulam Mustafa cell: +92 333.611.7681 sip: cyren...@ekiga.net mail: mustafa...@gmail.com web: cyrenity.wordpress.com
Re: mysql cluster with 3 db/data and 2 mgm nodes
Unless you have a very good reason, you probably shouldn't go with cluster in the first place. If it is HA you want to have, check out other options like MMM for MySQL (http://mysql-mmm.org), DRBD +Heartbeat and others. Can you tell us a bit more about your goals/desires? Walter Heck Engineer @ Open Query (http://openquery.com) On Mon, Aug 9, 2010 at 14:46, Ghulam Mustafa mustafa...@gmail.com wrote: Hi, i am about to configure mysql-cluster setup with 3 data+sql nodes and 2 mgm nodes, i would like to know if it's ok to go ahead with this setup, because somewhere i read it's preferred to setup _even_ number of data nodes instead e.g. 2, 4, or 6. please advice me. thanks and best regards, -m -- Ghulam Mustafa cell: +92 333.611.7681 sip: cyren...@ekiga.net mail: mustafa...@gmail.com web: cyrenity.wordpress.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: mysql cluster with 3 db/data and 2 mgm nodes
On Sun, Aug 8, 2010 at 11:49 PM, Walter Heck - OlinData.com li...@olindata.com wrote: Unless you have a very good reason, you probably shouldn't go with cluster in the first place. If it is HA you want to have, check out other options like MMM for MySQL (http://mysql-mmm.org), DRBD +Heartbeat and others. Can you tell us a bit more about your goals/desires? Walter Heck Engineer @ Open Query (http://openquery.com) Walter is spot on and yes, 3 is not a good number for data nodes. The only recommended (and somewhat well tested) number of replicas is 2, so 3 would not be useful. You may want to buy another box so that do 2 replicas with 2 shards, OR just use the third node as a warm standby. -- Rob Wultsch wult...@gmail.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
MySQL Cluster Out of fragment records (increase MaxNoOfOrderedIndexes)
Dear All, I want to add one column in my existing NDB table. While adding column in to the table I am getting this error:- | Level | Code | Message Error | 1296 | Got error 904 'Out of fragment records (increase MaxNoOfOrderedIndexes)' from NDB | | Error | 1005 | Can't create table 'ChitMeRegistration.User_1' (errno: 136) Whereas my ndb_mgm - is showing me only Node 3: Index usage is 2%(376 8K pages of total 16416) Node 3: Index usage is 2%(392 8K pages of total 16416) Node 3: Data usage is 1%(800 32K pages of total 40960) Node 4: Index usage is 2%(366 8K pages of total 16416) Node 4: Index usage is 2%(382 8K pages of total 16416) Node 4: Data usage is 1%(800 32K pages of total 40960) But still I am getting this error. Can anyone help me understanding how should I go about this error. As I have only few hundred records in my table and still i m getting this error. Thanks in advance. -- Regards, Manasi Save
RE: MySQL Cluster / NDB MyISAM mix
Thanks. Yes it's a delicate construct but tables like 'IP2Location' give me a headache as NDB tables. Yet I have to test if 7.0.X can handle it. -Original Message- From: Michael Dykman [mailto:mdyk...@gmail.com] Sent: Mittwoch, 14. Oktober 2009 17:33 To: Christian Meisinger Cc: mysql@lists.mysql.com Subject: Re: MySQL Cluster / NDB MyISAM mix I can think of no reason why this shouldn't work, My administrator colleagues would probably beat me with 2x4's for handing them such a delicate construct to maintain in production but it seems perfectly feasible to me :-) - michael dykman On Wed, Oct 14, 2009 at 11:03 AM, Christian Meisinger c.meisin...@livingliquid.com wrote: Hi guys. Ok lets say i've 2 server running MySQL, NDB node and NDB manager on each. Now I don't want to convert all tables to NDB instead I leave a few as MyISAM. Is it officially supported if I setup a master-master replication between the two MySQL instances and add ignore entries for all NDB tables? So basically I would convert all important tables to NDB and leave other tables as MyISAM, but they would still be 'synced' via replication. I've tested it and it look like it works... but... does it work by coincidence? :) Thanks, chris -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=mdyk...@gmail.com -- - michael dykman - mdyk...@gmail.com Dont worry about people stealing your ideas. If theyre any good, youll have to ram them down their throats! Howard Aiken -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
MySQL Cluster / NDB MyISAM mix
Hi guys. Ok lets say i've 2 server running MySQL, NDB node and NDB manager on each. Now I don't want to convert all tables to NDB instead I leave a few as MyISAM. Is it officially supported if I setup a master-master replication between the two MySQL instances and add ignore entries for all NDB tables? So basically I would convert all important tables to NDB and leave other tables as MyISAM, but they would still be 'synced' via replication. I've tested it and it look like it works... but... does it work by coincidence? :) Thanks, chris -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: MySQL Cluster / NDB MyISAM mix
I can think of no reason why this shouldn't work, My administrator colleagues would probably beat me with 2x4's for handing them such a delicate construct to maintain in production but it seems perfectly feasible to me :-) - michael dykman On Wed, Oct 14, 2009 at 11:03 AM, Christian Meisinger c.meisin...@livingliquid.com wrote: Hi guys. Ok lets say i've 2 server running MySQL, NDB node and NDB manager on each. Now I don't want to convert all tables to NDB instead I leave a few as MyISAM. Is it officially supported if I setup a master-master replication between the two MySQL instances and add ignore entries for all NDB tables? So basically I would convert all important tables to NDB and leave other tables as MyISAM, but they would still be 'synced' via replication. I've tested it and it look like it works... but... does it work by coincidence? :) Thanks, chris -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=mdyk...@gmail.com -- - michael dykman - mdyk...@gmail.com Don’t worry about people stealing your ideas. If they’re any good, you’ll have to ram them down their throats! Howard Aiken -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Mysql Cluster data node Setup
Hi All, I have Set up MySQL Cluster This is my Config.ini file #options affecting ndbd processes on all data nodes: [ndbd default] NoOfReplicas=2# Number of replicas DataMemory=80M# How much memory to allocate for data storage IndexMemory=18M # How much memory to allocate for index storage # For DataMemory and IndexMemory, we have used the # default values. Since the world database takes up # only about 500KB, this should be more than enough for # this example Cluster setup. # TCP/IP options: [tcp default] portnumber=2202 # This the default; however, you can use any port that is free # for all the hosts in the cluster # Note: It is recommended that you do not specify the port # number at all and allow the default value to be used instead # Management process options: [ndb_mgmd] hostname=192.168.1.1 # Hostname or IP address of management node datadir=/var/lib/mysql-cluster # Directory for management node log files # Options for data node A: [ndbd] # (one [ndbd] section per data node) hostname=192.168.1.1 # Hostname or IP address datadir=/usr/local/mysql/data # Directory for this data node's data files # Options for data node B: [ndbd] hostname=192.168.0.40 # Hostname or IP address datadir=/usr/local/mysql/data # Directory for this data node's data files # SQL node options: [mysqld] hostname=192.168.1.1 # Hostname or IP address # (additional mysqld connections can be # specified for this node for various # purposes such as running ndb_restore) when I try to start both data nodes it is not starting any. But when I start only one data node A (192.168.1.1) after commenting node B (192.168.0.40). It is starting fine. can any one provide any input how to fix this error. also what configuaration do I need to make on node B server. I have just set Management node information on node B server. Thanks in advance. -- Regards, Manasi Save -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
MySQL Cluster 6.3.20 has been released
Dear MySQL Cluster users, MySQL Cluster 6.3.20, a new version of the popular Open Source Database Management System, has been released. MySQL Cluster is a High Availability Database for Real-Time, Mission Critical Applications. The release is now available in source and binary form for a number of platforms (Linux, Solaris, Mac OS X) from our download pages at http://dev.mysql.com/downloads/cluster/ and mirror sites. Note that not all mirror sites may be up to date at this point in time, so if you can't find this version on some mirror, please try again later or choose another download site. We welcome and appreciate your feedback, bug reports, bug fixes, patches etc.: http://forge.mysql.com/wiki/Contributing The following section lists important, incompatible and security changes since the previous MySQL Cluster 6.3.17 release. The full changelog including many more fixes can be viewed online at http://dev.mysql.com/doc/refman/5.1/en/mysql-cluster-news-6-3.html This is a bugfix release which replaces MySQL Cluster 6.3.17. Please note: MySQL Cluster 6.3.17 was based on MySQL 5.1.27, MySQL Cluster 6.3.20 is based on MySQL 5.1.30 - so in addition to the changes to the cluster part (listed in this mail), the changes to the general server versions 5.1.28, 5.1.29, and 5.1.30 apply. Please find them at http://dev.mysql.com/doc/refman/5.1/en/news-5-1-x.html Functionality added or changed: * Cluster API: Important Change: MGM API applications exited without raising any errors if the connection to the management server was lost. The fix for this issue includes two changes: 1. The MGM API now provides its own SIGPIPE handler to catch the broken pipe error that occurs when writing to a closed or reset socket. This means that MGM API now behaves the same as NDB API in this regard. 2. A new function ndb_mgm_set_ignore_sigpipe() has been added to the MGM API. This function makes it possible to bypass the SIGPIPE handler provded by the MGM API. (Bug#40498) * Cluster Replication: Important Note: This release of MySQL Cluster derives in part from MySQL 5.1.29, where the default value for the --binlog-format option changed to STATEMENT. That change does not affect this or future MySQL Cluster NDB 6.x releases, where the default value for this option remains MIXED, since MySQL Cluster Replication does not work with the statement-based format. (Bug#40586) * MySQL Cluster: When performing an initial start of a data node, fragment log files were always created sparsely --- that is, not all bytes were written. Now it is possible to override this behavior using the new InitFragmentLogFiles configuration parameter. (Bug#40847) * MySQL Cluster: It is no longer a requirement for database autodiscovery that an SQL node already be connected to the cluster at the time that a database is created on another SQL node. It is no longer necessary to issue CREATE DATABASE (or CREATE SCHEMA) statements on an SQL node joining the cluster after a database is created in order for the new SQL node to see the database and any NDCLUSTER tables that it contains. (Bug#39612) Bugs fixed: * Cluster API: MySQL Cluster: Failed operations on BLOB and TEXT columns were not always reported correctly to the originating SQL node. Such errors were sometimes reported as being due to timeouts, when the actual problem was a transporter overload due to insufficient buffer space. (Bug#39867, Bug#39879) * MySQL Cluster: Undo logs and data files were created in 32K increments. Now these files are created in 512K increments, resulting in shorter creation times. (Bug#40815) * MySQL Cluster: Redo log creation was very slow on some platforms, causing MySQL Cluster to start more slowly than necessary with some combinations of hardware and operating system. This was due to all write operations being synchronized to disk while creating a redo log file. Now this synchronization occurs only after the redo log has been created. (Bug#40734) * MySQL Cluster: Transaction failures took longer to handle than was necessary. When a data node acting as transaction coordinator (TC) failed, the surviving data nodes did not inform the API node initiating the transaction of this until the failure had been processed by all protocols. However, the API node needed only to know about failure handling by the transaction protocol --- that is, it needed to be informed only about the TC takeover process. Now, API nodes (including MySQL servers acting as cluster SQL nodes) are informed as soon as the TC takeover is complete, so that it can carry on operating more quickly. (Bug#40697) * MySQL Cluster: It was theoretically possible for stale data to be read from NDBCLUSTER tables when the transaction isolation level was set to ReadCommitted. (Bug#40543) * MySQL Cluster
MySQL Cluster
Hi, Does anybody has a tip to install a MySQL Cluster in a Linux CentOS-5? Is it better from source or can it be from yum? I do prefer yum because it's easier for upgrades, but I don't know if the available package was compiled for that. Thank you, Ronan -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: MySQL Cluster
Hi. Here are some of my tests on Centos 5.0. http://blog.chinaunix.net/u/29134/article_71956.html On Fri, Nov 21, 2008 at 3:49 AM, Ronan Lucio [EMAIL PROTECTED] wrote: Hi, Does anybody has a tip to install a MySQL Cluster in a Linux CentOS-5? Is it better from source or can it be from yum? I do prefer yum because it's easier for upgrades, but I don't know if the available package was compiled for that. Thank you, Ronan -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- I'm a MySQL DBA in china. More about me just visit here: http://yueliangdao0608.cublog.cn
Re: MySQL Cluster
Hello Moon's Father, That would be great..if it was in english ;) Hi. Here are some of my tests on Centos 5.0. http://blog.chinaunix.net/u/29134/article_71956.html On Fri, Nov 21, 2008 at 3:49 AM, Ronan Lucio [EMAIL PROTECTED] wrote: Hi, Does anybody has a tip to install a MySQL Cluster in a Linux CentOS-5? Is it better from source or can it be from yum? I do prefer yum because it's easier for upgrades, but I don't know if the available package was compiled for that. Thank you, Ronan -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: MySQL Cluster
Thanks for advice. There're no environment for me to test the cluster again right now. Hope the chance chooses me, then the english version will be done. :) On Fri, Nov 21, 2008 at 10:48 AM, steve grosz [EMAIL PROTECTED]wrote: Hello Moon's Father, That would be great..if it was in english ;) Hi. Here are some of my tests on Centos 5.0. http://blog.chinaunix.net/u/29134/article_71956.html On Fri, Nov 21, 2008 at 3:49 AM, Ronan Lucio [EMAIL PROTECTED] wrote: Hi, Does anybody has a tip to install a MySQL Cluster in a Linux CentOS-5? Is it better from source or can it be from yum? I do prefer yum because it's easier for upgrades, but I don't know if the available package was compiled for that. Thank you, Ronan -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- I'm a MySQL DBA in china. More about me just visit here: http://yueliangdao0608.cublog.cn
