Privileges Provided by MySQL group_replication_set_communication_protocol()  functions. Grant this privilege to accounts that are used to administer servers that are members of a replication group. Enables the account to activate and deactivate redo log archiving. Enables use of the  ALTER INSTANCE {ENABLE|DISABLE} INNODB REDO_LOG  statement to enable or disable redo logging. Introduced in MySQL 8.0.21. See Disabling Redo Logging. Enables the user or role and its privileges to be shared and synchronized between all  NDB -enabled MySQL servers as soon as they join a given NDB Cluster. This privilege is available only if the  NDB storage engine is enabled. Any changes to or revocations of privileges made for the given user or role are synchronized immediately with all connected MySQL servers (SQL nodes). You should be aware that there is no guarantee that multiple statements affecting privileges originating from different SQL nodes are executed on all SQL nodes in the same order. For this reason, it is highly recommended that all user administration be done from a single designated SQL node. NDB_STORED_USER  is a global privilege and must be granted or revoked using  ON *.* . Trying to set any other scope for this privilege results in an error. This privilege can be given to most application and administrative users, but it cannot be granted to system reserved accounts such as mysql.session@localhost  or  mysql.infoschema@localhost . A user that has been granted the  NDB_STORED_USER  privilege is stored in  NDB  (and thus shared by all SQL nodes), as is a role with this privilege. A user that is merely granted a role that has NDB_STORED_USER  is  not  stored in  NDB ; each  NDB  stored user must be granted the privilege explicitly. For more detailed information about how this works in  NDB , see Section 23.5.12, “Distributed MySQL Privileges with NDB_STORED_USER” . The  NDB_STORED_USER  privilege is available beginning with NDB 8.0.18. For users who also have  SYSTEM_VARIABLES_ADMIN ,  PERSIST_RO_VARIABLES_ADMIN  enables use of  SET PERSIST_ONLY  to persist global system variables to the  mysqld-auto.cnf  option file in the data directory. This statement is similar to  SET PERSIST  but does not modify the runtime global system variable value. This makes  SET PERSIST_ONLY  suitable for configuring read-only system variables that can be set only at server startup. See also Section 5.1.9.1, “System Variable Privileges” . Enables the account to act as the  PRIVILEGE_CHECKS_USER  for a replication channel, and to execute BINLOG  statements in  mysqlbinlog  output. Grant this privilege to accounts that are assigned using CHANGE REPLICATION SOURCE TO  (from MySQL 8.0.23) or  CHANGE MASTER TO  (before MySQL 8.0.23) to provide a security context for replication channels, and to handle replication errors on those channels. As well as the  REPLICATION_APPLIER  privilege, you must also give the account 1198 • REPLICATION_APPLIER • PERSIST_RO_VARIABLES_ADMIN • NDB_STORED_USER • INNODB_REDO_LOG_ENABLE • INNODB_REDO_LOG_ARCHIVE