Syntax\n------\n\nSTART { SLAVE | REPLICA } ["connection_name"] [thread_type [, thread_type] ... ]\nSTART { SLAVE | REPLICA } ["connection_name"] [SQL_THREAD] UNTIL                \n    MASTER_LOG_FILE = 'log_name', MASTER_LOG_POS = log_pos \nSTART { SLAVE | REPLICA } ["connection_name"] [SQL_THREAD] UNTIL\n    RELAY_LOG_FILE = 'log_name', RELAY_LOG_POS = log_pos \nSTART { SLAVE | REPLICA } ["connection_name"] [SQL_THREAD] UNTIL\n    MASTER_GTID_POS = <GTID position> \nSTART ALL { SLAVES | REPLICAS } [thread_type [, thread_type]] \n\nthread_type: IO_THREAD | SQL_THREAD\n\nDescription\n-----------\n\nSTART REPLICA is a synonym for START SLAVE.\n\nOnly START SLAVE can be used.\n\nSTART SLAVE or START REPLICA with no thread_type options starts both of the slave threads (see replication) needed to connect with a master setup with CHANGE MASTER TO. 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.\n\nSTART SLAVE requires the REPLICATION SLAVE ADMIN privilege.\n\nSTART SLAVE requires the SUPER privilege.\n\nIf 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 (SHOW REPLICA STATUS).\n\nSTART SLAVE UNTIL\n\nSTART 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.\n\nSTART SLAVE UNTIL master_gtid_pos=xxx is also supported. See Global Transaction ID/START SLAVE UNTIL master_gtid_pos=xxx for more details.\n\nMariaDB starting with 11.3.0\n\nSQL_BEFORE_GTIDS|SQL_AFTER_GTIDS\n\nThe START SLAVE UNTIL statement contains the options SQL_BEFORE_GTIDS and SQL_AFTER_GTIDS to allow control of whether the slave stops before or after a provided GTID state. Its syntax is:\n\n``sql\nSTART SLAVE UNTIL (SQL_BEFORE_GTIDS|SQL_AFTER_GTIDS)="<gtid_list>"\n`\n\nSee Global Transaction ID#SQL_BEFORE_GTIDS/SQL_AFTER_GTIDS for details.\n\nSQL_BEFORE_GTIDS and SQL_AFTER_GTIDS are not available.\n\nconnection_name\n\nIf there is only one nameless master, or the default master (as specified by the default_master_connection system variable) is intended, connection_name can be omitted. If provided, the START SLAVE statement will apply to the specified master. connection_name is case-insensitive.\n\nThe FOR CHANNEL keyword is available for MySQL compatibility. This is identical to using the channel_name directly after START SLAVE.\n\nThe FOR CHANNEL keyword is not available.\n\nSTART ALL SLAVES\n\nSTART 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.\n\nURL: https://mariadb.com/docs/server/reference/sql-statements/administrative-sql-statements/replication-statements/start-replica