MySQL Bugs: #38328: Docs for START SLAVE need improvement (SQL vs I

Bug #38328	Docs for START SLAVE need improvement (SQL vs I_O)
Submitted:	24 Jul 2008 5:33	Modified:	24 Jul 2008 15:57
Reporter:	Jon Stephens	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Documentation	Severity:	S3 (Non-critical)
Version:	All	OS:	Any
Assigned to:	Jon Stephens	CPU Architecture:	Any

Description:
Sven Sandberg wrote:
> Hi!
> 
> Could you clarify the following in the documentation for START SLAVE 
> (http://dev.mysql.com/doc/refman/5.1/en/start-slave.html):
> 
> START SLAVE sends ack to the user after both the IO thread and the SQL 
> thread have started. However, the IO thread may not have connected. 
> Hence, immediately after START SLAVE, it is guaranteed that SHOW SLAVE 
> STATUS shows Slave_SQL_Runing=Yes, but it is not guaranteed that it 
> shows Slave_IO_Running=Yes (because Slave_IO_Running=Yes only if the IO 
> thread is running and connected).
> 
> Also, in the section about @@init_slave at 
> http://dev.mysql.com/doc/refman/5.1/en/server-system-variables.html#option_mysqld_init_sla... 
> , it would be good to clarify that the SQL thread sends ack to the 
> client before @@init_slave is executed. So it is not guaranteed that 
> @@init_slave has been executed when START SLAVE returns.

How to repeat:
See Description.

Suggested fix:
Make indicated fixes to docs.

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.