The Ultimate Guide to High Availability with MariaDB

START SLAVE

You are viewing an old version of this article. View the current version here. 
START SLAVE ["connection_name"] [thread_type [, thread_type] ... ]
START SLAVE ["connection_name"] [SQL_THREAD] UNTIL                
    MASTER_LOG_FILE = 'log_name', MASTER_LOG_POS = log_pos
START SLAVE ["connection_name"] [SQL_THREAD] UNTIL
    RELAY_LOG_FILE = 'log_name', RELAY_LOG_POS = log_pos
START SLAVE ["connection_name"] [SQL_THREAD] UNTIL
    MASTER_GTID_POS = <GTID position>
START ALL SLAVES [thread_type [, thread_type]]
thread_type: IO_THREAD | SQL_THREAD

START SLAVE with no thread_type options starts both of the slave threads (see replication). The I/O thread reads events from the master server and stores them in the relay log. The SQL thread reads events from the relay log and executes them. START SLAVE requires the SUPER privilege.

If START SLAVE succeeds in starting the slave threads, it returns without any error. However, even in that case, it might be that the slave threads start and then later stop (for example, because they do not manage to connect to the master or read its binary log, or some other problem). START SLAVE does not warn you about this. You must check the slave's error log for error messages generated by the slave threads, or check that they are running satisfactorily with SHOW SLAVE STATUS.

START SLAVE UNTIL refers to the SQL THREAD slave position at which the SQL THREAD replication will halt. If SQL_THREAD isn't specified both threads are started.

MariaDB starting with 10.0

START ALL SLAVES starts all configured slaves (slaves with master_host not empty) that were not started before. It will give a note for all started connections. You can check the notes with SHOW WARNINGS.

MariaDB starting with 10.0.2

Since version 10.0.2, START SLAVE UNTIL master_gtid_pos=xxx is also supported, see Global Transaction ID/START SLAVE UNTIL master_gtid_pos=xxx for more details.

See also

  • CHANGE MASTER TO is used to create and change connections.
  • STOP SLAVE is used to stop a running connection.
  • RESET SLAVE is used to reset parameters for a connection and also to permanently delete a master connection.

Comments

Comments loading...
Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.