MySQL Cluster Tutorial - cdn.oreillystatic.com

3. Fetch the port parameter to connect to mysqld with ID=7:
mcm> get -d port:mysqld:7 mycluster;
+------+-------+----------+------+----------+------+---------+---------+
| Name | Value | Process1 | Id1 | Process2 | Id2 | Level | Comment |
+------+-------+----------+------+----------+------+---------+---------+
| port | 3306 | mysqld | 7 | | | Default | |
+------+-------+----------+------+----------+------+---------+---------+
4. Turn off privilege checking for all MySQL Servers and change the port for connecting to
the mysqld with ID = 8 to 3307. Allow data nodes to be automatically restarted after
they fail:
mcm> set skip-grant-tables:mysqld=true,port:mysqld:8=3307,StopOnError:ndbd=false
mycluster;
MySQL Cluster Manager automatically determines which nodes (processes) need to be
restarted and in which order to make the change take effect but avoid loss of service. In
this example, this results in each management, data and MySQL Server node being
restarted sequentially as shown in Figure 6 below.
Figure 6: MySQL Cluster nodes automatically restarted after configuration change
Upgrading MySQL Cluster
Upgrading MySQL Cluster when using MySQL Cluster Manager is extremely simple. The
amount of administrator time needed and the opportunities for human error are massively
reduced.
There are three prerequisites before performing the upgrade:
1. Ensure that the upgrade path that you are attempting to perform is supported; by
referring to http://dev.mysql.com/doc/mysql-cluster-excerpt/5.1/en/mysql-clusterupgrade-downgrade-compatibility.html.
If not then you will need to perform an upgrade to an intermediate version of MySQL
Cluster first;
Copyright © 2010, Oracle and/or its affiliates. All rights reserved. 31/81