MySQL Bugs: #40361: Please document RESET MASTER more clearly

Bug #40361	Please document RESET MASTER more clearly
Submitted:	27 Oct 2008 20:38	Modified:	28 Oct 2008 20:23
Reporter:	Sven Sandberg	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:
RESET MASTER is not supposed to be executed when there are running slaves. The behavior of the slaves is undefined (the slave threads may hang). It should be mentioned in the documentation that RESET MASTER must not be executed with running slaves.

I'd also suggest adding a clarification of the differences between RESET MASTER and PURGE MASTER LOGS. After RESET MASTER, the next binlog file will be master-bin.000001, whereas the number will not be reset by PURGE MASTER LOGS. Plus PURGE MASTER LOGS is safe to execute when there are slaves (as already described in the section about PURGE MASTER LOGS).

It may be enlightening to give the intended use case too. The purpose of RESET MASTER is to get a clean binlog when the master server is started for the first time. In particular, you may setup the master and slave, run a few queries on master just to verify the setup, and then start using the servers for real. Then RESET MASTER can be used to clean up the experimental queries.

How to repeat:
-

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.