SHUTDOWN [WAIT FOR ALL SLAVES]
SHUTDOWN command shuts the server down.
WAIT FOR ALL SLAVES
When a master server is shutdown and it goes through the normal shutdown process, the master kills client threads in random order. By default, the master also considers its binary log dump threads to be regular client threads. As a consequence, the binary log dump threads can be killed while client threads still exist, and this means that data can be written on the master during a normal shutdown that won't be replicated. This is true even if semi-synchronous replication is being used.
SHUTDOWN WAIT FOR ALL SLAVES;
WAIT FOR ALL SLAVES option is provided, the server only kills its binary log dump threads after all client threads have been killed, and it only completes the shutdown after the last binary log has been sent to all connected slaves.
See Replication Threads: Binary Log Dump Threads and the Shutdown Process for more information.
Shutdown for Upgrades
The following example shows how to create an event which turns off the server at a certain time:
CREATE EVENT `test`.`shutd` ON SCHEDULE EVERY 1 DAY STARTS '2014-01-01 20:00:00' COMMENT 'Shutdown Maria when the office is closed' DO BEGIN SHUTDOWN; END;
Other Ways to Stop mysqld
You can use the mysqladmin shutdown command to take down mysqld cleanly.
You can also use the system kill command on Unix with signal SIGTERM (15)
kill -SIGTERM pid-of-mysqld-process
You can find the process number of the server process in the file that ends with
.pid in your data directory.
The above is identical to
On windows you should use:
NET STOP MySQL