MySQL Bugs: #51152: reset master to have soft and hard options

Bug #51152	reset master to have soft and hard options
Submitted:	12 Feb 2010 20:58
Reporter:	Andrei Elkin	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Server: Replication	Severity:	S4 (Feature request)
Version:	5.0+	OS:	Any
Assigned to:	Assigned Account	CPU Architecture:	Any
Tags:	RESET MASTER

Description:
RESET MASTER is not well-defined if the command is issued while there is a connected slave. The docs say
*note `RESET MASTER': reset-master. is _not_ intended to be used
while any replication slaves are running. The behavior of
 `RESET MASTER' when used while slaves are running
is undefined.

However, it is possible to define that properly.

1. to introduce an option to the command that 
   would force to execute RESET MASTER even though the master
   is connected to a slave
e.g
   RESET MASTER FORCE

2. without the option put, that is

   RESET MASTER 

   should not attempt its operations if there is at least one connected slave,
   and error out instead.

Notice that the current behaviour is brute force removing binlog files to ignore possible connected slave.
slave.

How to repeat:
See docs.

Suggested fix:
See the description.