does not support repeatable reads, which can cause problems with the restoration process.
NDB
Although the backup process is "hot", restoring a MySQL Cluster from backup is not a 100% "hot"
process. This is due to the fact that, for the duration of the restore process, running transactions get
nonrepeatable reads from the restored data. This means that the state of the data is inconsistent while
the restore is in progress.
17.5.4. MySQL Server Usage for MySQL Cluster
is the traditional MySQL server process. To be used with MySQL Cluster,
mysqld
be built with support for the
from http://dev.mysql.com/downloads/. If you build MySQL from source, you must invoke
with the
--with-ndbcluster
For information about other MySQL server options and variables relevant to MySQL Cluster in addition
to those discussed in this section, see
MySQL
Cluster".
If the
mysqld
disabled by default. You can use either of two possible options to enable this engine:
• Use
--ndbcluster
• Insert a line containing
An easy way to verify that your server is running with the
issue the
SHOW ENGINES
as the
Support
displayed in the output, you are not running an NDB-enabled version of MySQL. If you see
in this row, you need to enable it in either one of the two ways just described.
To read cluster configuration data, the MySQL server requires at a minimum three pieces of
information:
• The MySQL server's own cluster node ID
• The host name or IP address for the management server (MGM node)
• The number of the TCP/IP port on which it can connect to the management server
Node IDs can be allocated dynamically, so it is not strictly necessary to specify them explicitly.
The
mysqld
command line when starting
address where the management server can be found, as well as the TCP/IP port it uses.
In the following example,
and the management server listens for cluster messages on port 1186:
shell>
mysqld --ndbcluster --ndb-connectstring=ndb_mgmd.mysql.com:1186
See
Section 17.3.2.2, "The MySQL Cluster
Given this information, the MySQL server will be a full participant in the cluster. (We often refer to a
process running in this manner as an SQL node.) It will be fully aware of all cluster data nodes
mysqld
as well as their status, and will establish connections to all data nodes. In this case, it is able to use any
data node as a transaction coordinator and to read and update node data.
You can see in the
PROCESSLIST. If the MySQL server is connected to the cluster, and you have the
privilege, then the first row of the output is as shown here:
MySQL Server Usage for MySQL Cluster
NDBCLUSTER
option to enable
binary has been built with Cluster support, the
[1610]
as a startup option on the command line when starting mysqld.
NDBCLUSTER
statement in the MySQL Monitor (mysql). You should see the value
value in the row for NDBCLUSTER. If you see
parameter
ndb-connectstring
mysqld
ndb_mgmd.mysql.com
client whether a MySQL server is connected to the cluster using
mysql
storage engine, as it is in the precompiled binaries available
NDB Cluster
Section 17.3.4, "MySQL Server Options and Variables for
in the
section of your
[mysqld]
NDBCLUSTER
is used to specify the connectstring either on the
or in my.cnf. The connectstring contains the host name or IP
is the host where the management server resides,
Connectstring", for more information on connectstrings.
1660
mysqld
storage engine support.
storage engine is still
NDBCLUSTER
file.
my.cnf
storage engine enabled is to
in this row or if there is no such row
NO
PROCESS
needs to
configure
YES
DISABLED
SHOW
[577]
Need help?
Do you have a question about the 5.0 and is the answer not in the manual?
Questions and answers