The terms master and slave have historically been used in replication, but the terms terms primary and replica are now preferred. The old terms are used still used in parts of the documentation, and in MariaDB commands, although MariaDB 10.5 has begun the process of renaming. The documentation process is ongoing. See MDEV-18777 to follow progress on this effort.
STOP SLAVE ["connection_name"] [thread_type [, thread_type] ... ] [FOR CHANNEL "connection_name"] STOP ALL SLAVES [thread_type [, thread_type]] STOP REPLICA ["connection_name"] [thread_type [, thread_type] ... ] -- from 10.5.1 STOP ALL REPLICAS [thread_type [, thread_type]] -- from 10.5.1 thread_type: IO_THREAD | SQL_THREAD
Like START SLAVE, this statement may be used with the
SQL_THREAD options to name the thread or threads to be stopped. In almost all cases, one never need to use the
STOP SLAVE waits until any current replication event group affecting
one or more non-transactional tables has finished executing (if there
is any such replication group), or until the user issues a KILL QUERY or KILL CONNECTION statement.
STOP SLAVE doesn't delete the connection permanently. Next time you execute START SLAVE or the MariaDB server restarts, the replica connection is restored with it's original arguments. If you want to delete a connection, you should execute RESET SLAVE.
STOP ALL SLAVES
STOP ALL SLAVES stops all your running replicas. It will give you a
note for every stopped connection. You can check the notes with SHOW WARNINGS.
connection_name option is used for multi-source replication.
If 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
STOP SLAVE statement will apply to the specified master.
connection_name is case-insensitive.
MariaDB starting with 10.7.0
FOR CHANNEL keyword was added for MySQL compatibility. This is identical as
using the channel_name directly after