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 throughout the documentation, and in MariaDB commands, although MariaDB 10.5 has begun the process of renaming. The documentation will follow over time. See MDEV-18777 to follow progress on this effort.
A common replication setup is to have the slaves read-only to ensure that no one accidentally updates them. If the slave has binary logging enabled and gtid_strict_mode is used, then any update that causes changes to the binary log will stop replication.
When the variable
read_only is set to 1, no updates are permitted except from users with the SUPER privilege or slave servers updating from a master. Inserting rows to log tables, updates to temporary tables and OPTIMIZE TABLE or ANALYZE TABLE statements are excluded from this limitation.
If read_only is set to 1, then the SET PASSWORD statement is limited only to users with the SUPER privilege.
Attempting to set the
read_only variable to 1 will fail if the current session has table locks or transactions pending.
The statement will wait for other sessions that hold table locks. While the attempt to set read_only is waiting, other requests for table locks or transactions will also wait until read_only has been set.
Starting with MariaDB 10.3.20 we have fixed some issues related to read only slaves:
- CREATE, DROP, ALTER, INSERT and DELETE of temporary tables are not logged to binary log, even in statement or mixed mode. With earlier MariaDB versions, one can avoid the problem with temporary tables by using binlog_format=ROW in which cases temporary tables are never logged.
- Changes to temporary tables created during
read_onlywill not be logged even after
read_onlymode is disabled (for example if the slave is promoted to a master).
- The Admin statements ANALYZE, CHECK and REPAIR will not be logged to the binary log under read-only.
Older MariaDB Versions
If you are using an older MariaDB version with read-only slaves and binary logging enabled on the slave, and you need to do some changes but don't want to have them logged to the binary log, the easiest way to avoid the logging is to disable binary logging while running as root during maintenance:
set sql_log_bin=0; alter table test engine=rocksdb;
The above changes the test table on the slave to rocksdb without registering the change in the binary log.