MySQL Cluster Tutorial - cdn.oreillystatic.com

The above picture shows one MySQL server doing binary logging. It does does by listening
for events through NDB Injector-Thread.
The above shown setup has one flaw, we’ll see later what.
Enabling Binary Logging
You can enable the binary logging in any SQL Node. Here is an example from the
configuration files used in this tutorial:
[mysqld]
ndbcluster
log_bin = master_A_binlog
server_id = 1
binlog_format = MIXED
The --log-bin option enables the binary logging into files named master_A_binlog. The -binlog-format
is not really needed, but it’s good to be explicit. Here is how the files look
like:
master_A_binlog.000011
master_A_binlog.000012
master_A_binlog.index
Don’t forget to set the --server-id option to a value unique to each SQL Node
participating in the MySQL Cluster. If you don’t do this, replication will not work.
You can check the content of a binary log using the mysqlbinlog tool. Reading Row-Based
or Mixed binary logs might be a bit difficult. Take for example the following table:
CREATE TABLE attendees (
id INT UNSIGNED NOT NULL AUTO_INCREMENT,
email VARCHAR(200),
PRIMARY KEY (id)
) ENGINE=NDBCluster;
Lets insert some data:
INSERT INTO attendees (email) VALUES ('geert@localhost')
Reading the binary log, you don’t get the SQL statement:
shell> mysqlbinlog master_A_binlog.00001
..
BINLOG '
Xz/CSxMBAAAAMwAAAO8DAAAAACUAAAAAAAEABHRlc3QACWF0dGVuZGVlcwACAw8CyAAC
Xz/CSxMBAAAAPgAAAC0EAAAAABAAAAAAAAEABW15c3FsABBuZGJfYXBwbHlfc3RhdHVzAAUDCA8I
CAL/AAA=
Xz/CSxcBAAAAOwAAAGgEAAAAABAAAAAAAAAABR/gAQAAAA8AAACiAAAAAAAAAAAAAAAAAAAAAAAA
AAA=
Xz/CSxcBAAAAMgAAAJoEAAAQACUAAAAAAAEAAgP8AQAAAA9nZWVydEBsb2NhbGhvc3Q=
'/*!*/;
..
Copyright © 2010, Oracle and/or its affiliates. All rights reserved. 74/81