Replication and Binary Logging Options and Variables Type Boolean Default Value OFF Due to concurrency issues, a replica can become inconsistent when a transaction contains updates to both transactional and nontransactional tables. MySQL tries to preserve causality among these statements by writing nontransactional statements to the transaction cache, which is flushed upon commit. However, problems arise when modifications done to nontransactional tables on behalf of a transaction become immediately visible to other connections because these changes may not be written immediately into the binary log. The  binlog_direct_non_transactional_updates  variable offers one possible workaround to this issue. By default, this variable is disabled. Enabling  binlog_direct_non_transactional_updates causes updates to nontransactional tables to be written directly to the binary log, rather than to the transaction cache. As of MySQL 8.0.14, setting the session value of this system variable is a restricted operation. The session user must have privileges sufficient to set restricted session variables. See Section 5.1.9.1, “System Variable Privileges” . binlog_direct_non_transactional_updates  works only for statements that are replicated using the statement-based binary logging format ; that is, it works only when the value of  binlog_format is  STATEMENT , or when  binlog_format  is  MIXED  and a given statement is being replicated using the statement-based format. This variable has no effect when the binary log format is  ROW , or when binlog_format  is set to  MIXED  and a given statement is replicated using the row-based format. Before enabling this variable, you must make certain that there are no dependencies between transactional and nontransactional tables; an example of such a dependency would be the statement  INSERT INTO myisam_table SELECT * FROM innodb_table . Otherwise, such statements are likely to cause the replica to diverge from the source. This variable has no effect when the binary log format is  ROW  or  MIXED . Enables encryption for binary log files and relay log files on this server.  OFF  is the default.  ON  sets encryption on for binary log files and relay log files. Binary logging does not need to be enabled on the server to enable encryption, so you can encrypt the relay log files on a replica that has no binary log. To use encryption, a keyring plugin must be installed and configured to supply MySQL Server’s keyring service. For instructions to do this, see Section 6.4.4, “The MySQL Keyring” . Any supported keyring plugin can be used to store binary log encryption keys. • binlog_encryption Important Command-Line Format --binlog-encryption[={OFF|ON}] Introduced 8.0.14 System Variable binlog_encryption Scope Global Dynamic Yes SET_VAR  Hint Applies No Type Boolean Default Value OFF 3548