MySQL Bugs: #32691: Instructions for adding replication slaves incomplete

Bug #32691	Instructions for adding replication slaves incomplete
Submitted:	24 Nov 2007 8:35	Modified:	30 Nov 2007 21:26
Reporter:	Jon Stephens	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Documentation	Severity:	S2 (Serious)
Version:	5.0 (probably all)	OS:	Any
Assigned to:	Jon Stephens	CPU Architecture:	Any
Tags:	--relay-log, --relay-log-index, replication, slaves

Description:
(Excerpt from Mark Leith's email:)

[Try] to follow the instructions here:

http://dev.mysql.com/doc/refman/5.0/en/replication-howto-additionalslaves.html

Unfortunately, this [doesn't] fully work... On starting the instance on the copied slave the server [cannot] find the right files, as the relay index files are started with the hostname within them by default if --relay-log and --relay-log-index are not specified.

...

In order to copy a slave to another slave system, you should first ensure that --relay-log and --relay-log-index are set to generic names on the first slave.

Alternately, if this has not been done, you can:

o STOP SLAVE;
o Copy the contents the first slaves relay log index file to the top of the new slaves new relay log index file
o START SLAVE;

These should be clarified within the above page...

One other note on the above page:

1. Shut down the existing slave (slavea):

We mention 'slavea' at the end here, yet do not mention slavea (nor another slaveb etc.) in the entire page. I wonder what the point of (slavea) is in the above. 

How to repeat:
See Description

Suggested fix:
See Description

Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant products.