The binaries for MySQL Cluster 7.0.7 have now been released and can be downloaded from http://dev.mysql.com/downloads/cluster/7.0.html
A description of all of the changes (fixes) that have gone into MySQL Cluster 7.0.7 (compared to 7.0.6) can be found in the MySQL Cluster 7.0.7 Change Log.
Considering that you have the following hosts and MySQL Cluster
deployed in the following ways:
A: ndb_mgmd, ndbd , mysqld
B: ndb_mgmd, ndbd , mysqld
Now you have a couple of options on how to handle potential
network partitioning/split brain which could occur if the
computer A and B lose contact with each other. Let's see the
implications of these options.
Option 1: ArbitrationRank=1, no NIC bonding
MySQL Cluster 7.0.7 was released as a source distribution 1st of
Sept 2009. You should upgrade if you can build from source or use
the Configurator.
The Configurator v2.9 has been updated to use this
version.
If you are already using the Configurator and build from source
you can upgrade from MySQL Cluster 7.0.6 to 7.0.7 (and you are
recommended to upgrade because of the following changes/fixes) in four steps. Here is
how:
1. run the upgrade-706-to-707-src.sh script (put it in
install/ and chmod u+x ./upgrade-706-to-707-src.sh):
[cluster01]# …[Read more]
Update: As explained in “MySQL Cluster 7.0.7 binaries released” you can now download the compiled binaries for your particular platform. I am going to leave this entry in place as it will hopefully be useful for future releases but for 7.0.7 you should refer to that other post.
You’ll need to wait for the pre-built binaries but you can now download the source code and build it for yourself to get started. This article explains where to get it and how to build, install and test the installation.
In this example, I’ve used Ubuntu.
The first step is to download the compressed tar ball containing the source code by pointing your browser to …
[Read more]
Jonas just wrote a patch to this bug
on OPTIMIZE TABLE, and the issue that was also discussed in this
blog post. Jonas also fixed this bug
when he was at it.
Before, OPTIMIZE TABLE hardly freed up any pages and
to defragment you had to do a rolling restart of the data
nodes.
Now, there is only a 2% discrepancy between OPTIMIZE
TABLE and doing a rolling restart. This is great
stuff.
This will fix will make it into 6.3.26 and 7.0.7.
See below for details:
Creating two tables, t5 and t6:
CREATE TABLE `t5` (
`id` varchar(32) CHARACTER SET utf8 NOT NULL,
`name` varchar(32) …
Currently a number of users has reported upgrade issues on 6.3.x
to 7.0.6 (below is an example what might happen to you).
Thus, we don't recommend you to upgrade from 6.3.x to 7.0.6 in a
production system yet.
However, we are very interested in bug reports and and help with
testing.
We are also of course working on fixing these issues and will
keep you posted when things has improved. Sorry for the
inconvenience.
Currently the "best practice" to upgrade is to:
1) backup / mysqldump
2) start cluster 7.0.6 with initial so it is completely
blank
3) restore backup / load dump
ERROR 1005 (HY000): Can't create table 'test.#sql-3d25_aa905'
(Errno: 140)
mysql> show warnings;
+-------+------+--------------------------------------------------------------------------+
| Level | Code | Message |
…
Mat Keep and I will be presenting a Webinar on Wednesday, August 12, 2009 describing the new capabilities of MySQL Cluster 7.0. The time is designed to be Asia/Australasia-friendly but of course it’s open to everyone.
Register for the MySQL Cluster 7 Webinar here.
By attending this webinar, you will learn more about the next generation of MySQL Cluster, and how it enables you to deliver 99.999% database availability, with real time performance and linear scalability, while slashing TCO.
Boasting a range of breakthrough capabilities, MySQL Cluster 7.0 will enable you to stay ahead of your most demanding, mission-critical application requirements. Enhanced scalability delivers higher database performance with fewer nodes to simplify deployment and administration. Expanded platform support and interoperability delivers more …
[Read more]
At a customer I have had the opportunity to work with some really
state of the art equipment.
The customer is in the online gaming industry and we are building
a platform based on MySQL Cluster where we are consolidating a
number of applications. Workload is mainly inserts, updates, pk
reads, and index scans (quite frequent), and a few joins. The
cluster handles the transient data (current working set), and is
replicating to a long term data store (following this approach), and we are also feeding other
back-end support systems from this.
The cluster (>8 computers) is interconnected with Dolphin DX adapters. Computers are SUNs Nehalem …
Restarts are required for certain, infrequent maintenance activities. Note that there is no loss of service while a single node restarts.
When a data node restarts, it first attempts to load the data into memory from the local log files and then it will catch up with any subsequent changes by retrieveing them from the surviving node(s) in its node group.
Based on this, you would expect the time taken to restart a data node to be influenced by:
The times will also be influenced bycertain configuration parameters, performance of the host machine and whether the multi-threaded data node (ndbmtd) is being used.
To provide some insight into how these …
[Read more]NDB API Documentation
A new page has been added to this site: NDB API Docs which presents the information
from the header files for both the NDB API and the NDB Management
API.
The material has been generated using doxygen and will be
refreshed shortly after any new major, minor or maintenance
release is made generally available (starting from MySQL Cluster
7.0.6).
