Errata

MySQL High Availability

Errata for MySQL High Availability

Submit your own errata for this product.

The errata list is a list of errors and their corrections that were found after the product was released.

The following errata were submitted by our customers and have not yet been approved or disproved by the author or editor. They solely represent the opinion of the customer.

Color Key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update

Version Location Description Submitted by Date submitted
PDF Page 24
After the first paragraph, under "slave>"

The third line under "CHANGE MASTER TO" has the wrong MASTER_USER. It should read like this:

-> MASTER_USER = 'repl_user',

 smoothtommy  Jul 14, 2010 
Other Digital Version 25
Not sure

I'm not sure what page this is on (I have an electronic copy via Amazon). This is a general comment on the author's use of the replicant python library. At no point does the author import the library or provide a full code example. I have yet been able to import the library correctly even though during install the tests all pass. Based on the tests being run, import mysql.replicant should work, but it does not. In my site-packages there is a mysql/replicant directory with the various modules in there.
This library seems very useful (and is a primary reason I purchased the book). However, if the library cannot be used, the python examples in the book become more of a distraction than an actual feature.

 Mike Brannigan  Apr 30, 2013 
PDF Page 26
First paragraph under "new-slave>"

In the third line under "CHANGE MASTER TO", the "MASTER_USER" line is wrong. It should read like this:

-> MASTER_USER = 'repl_user'

This mistake exists on page 24 and 26. On page 5, we create 'repl_user'. On page 6, we use 'repl_user' in a "CHANGE MASTER TO" statement. Therefore, on pages 24 and 26, we should be consistent and use 'repl_user' again in those "CHANGE MASTER TO" statements.

smoothtommy  Jul 14, 2010 
Printed Page 34
last paragraph

The following line has a problem . It suggests as all the next steps needs to be performed . However it should be that any one of these steps is required .


Original :-Use the following to create a backup of InnoDB tables safely

1. Shut down the server and copy the files. This can be an advantage
if the database is big, as restoring data with mysqldump can be slow.
2. Use mysqldump after performing FLUSH TABLES WITH READ LOCK (as
we did earlier).
3. Use a snapshot solution such as LVM (on Linux) or ZFS (Zettabyte
File System) snapshots (on Solaris) after using FLUSH TABLES WITH
READ LOCK.

Corrected :-Use any one of the following to create a backup of InnoDB tables safely


 PAWAN GAUR  Jan 04, 2011 
Printed Page 40
2rd paragraph

In 2rd paragraph:

report> START SLAVE UNTIL
-> MASTER_LOG_POS = 'capulet-bin.000004',
-> MASTER_LOG_POS = 2650:

should be:

report> START SLAVE UNTIL
-> MASTER_LOG_FILE = 'capulet-bin.000004',
-> MASTER_LOG_POS = 2650:

 Yubei Zhu  Feb 05, 2012 
Printed Page 40
line 3 of 3rd paragraph

I think "STOP SLAVE UNTIL" should be: "START SLAVE UNTIL"

 Yubei Zhu  Feb 05, 2012 
Printed Page 62
Example 3-5

the definition of table log,it writes:

CREATE TABLE log (
id INT AUTO_INCREMENT,
email CHAR(64),
message TEXT,
ts TIMESTAMP,
PRIMARY KEY (id)
);


and i think it should be(missing a 'status' field):

CREATE TABLE log (
id INT AUTO_INCREMENT,
email CHAR(64),
status CHAR(64),
message TEXT,
ts TIMESTAMP,
PRIMARY KEY (id)
);

 Anonymous  Sep 13, 2010