Introduction

These commands allow fast promotion of a slave to a master. It is fast because it can be done without restarting the slave. Storage engines with dirty pages, such as InnoDB, can take a long time (more than a minute) to shutdown.

Features in the V1 and V2 patch

MAKE MASTER REVOKE SESSION
MAKE MASTER REVOKE SESSION WITH KILL
MAKE MASTER GRANT SESSION

Features only in the V1 patch

SQL statements include:

MAKE MASTER MASTER_LOG_FILE=<log_file>, MASTER_SERVER_ID=<id> BINLOG
MAKE MASTER MASTER_LOG_FILE=<log_file>, MASTER_SERVER_ID=<id>, INDEX=<log_file.index> BINLOG

MAKE MASTER MASTER_LOG_FILE ...

This enables the use of the binlog on a slave without restarting mysqld.

MAKE MASTER REVOKE SESSION

This prevents non-SUPER users from connecting. When the WITH KILL option is used, current non-SUPER connections are killed.

MAKE MASTER GRANT SESSION

This allows non-SUPER users to connect.

Comment by jana.poornavel, Apr 03, 2008

Mark, Sorry to say, the wiki actually doesnt help, when tried using your statements in the mysql client, they dont actually work. can you help in this regard. once i get to do it correctly, i ll come back and make the post a bit more elaborate. the questions i have are, 1)what does <log_file> stand for, is it a new log file name what we have to give it to the slave,so that starts writing bin log in that file 2)what does id stand for, does it stand for the current slave server's id 3)does the statement have to finish with bin log.

i have pasted the statement which i gave in my setup for your reference

MAKE MASTER MASTER_LOG_FILE=/var/lib/mysql3308/mysql3308134.bin, MASTER_SERVER_ID=1463308 BINLOG;

Comment by jana.poornavel, Apr 03, 2008

Mark, I think I have found out what is the issue. I havent successfully applied the MySQL5.x patch on top my current setup.