Reading the binary log. mysqlbinlog displays row-based events in the binary log using the BINLOG statement (see Section 13.7.6.1, “BINLOG Syntax”). This statement displays an event in printable form, but as a base 64-encoded string the meaning of which is not evident. When invoked with the --base...
Recommended Starting Configuration for MySQL Cluster Achieving the best performance from a MySQL Cluster depends on a number of factors including the following: • MySQL Cluster software version • Numbers of data nodes and SQL nodes • Hardw...
Redo log over-commit handling. It is possible to control a data node's handling of operations when too much time is taken flushing redo logs to disk. This occurs when a given redo log flush takes longer than RedoOverCommitLimit [2246] seconds, more than RedoOverCommitCounter [2245] times, causing...
Reducing Redundant I/O InnoDB has a number of settings that let you choose the balance between high reliability in case of a crash, and the amount of I/O overhead during high write workloads. For example, consider setting the configuration option...
Reducing Transactional Overhead The default value of 1 for the configuration options daemon_memcached_r_batch_size [1736] and daemon_memcached_w_batch_size [1737] is intended for maximum reliability of results and safety of stored or updated data. Depending on the type of application, you might ...
Replica. This is a copy of a cluster partition. Each node in a node group stores a replica. Also sometimes known as a partition replica. The number of replicas is equal to the number of nodes per node group. The following diagram illustrates a M...
Replication and AUTO_INCREMENT Statement-based replication of AUTO_INCREMENT, LAST_INSERT_ID() [1290], and TIMESTAMP values is done correctly, subject to the following exceptions: • When using statement-based replication prior to MySQL 5.6.10, AUTO_INCREMENT columns in tables on the slave must m...
Replication and Binary Logging Options and Variables The next few sections contain information about mysqld options and server variables that are used in replication and for controlling the binary log. Options and variables for use on replica...
Replication and BLACKHOLE Tables The BLACKHOLE storage engine accepts data but discards it and does not store it. When performing binary logging, all inserts to such tables are always logged, regardless of the logging format in use. Updates and deletes are handled differently depending on whether...
Replication and Character Sets The following applies to replication between MySQL servers that use different character sets: • If the master uses MySQL 4.1, you must always use the same global character set and collation on the master and the slave, regardless of the slave MySQL version. (These a...
