PDF (US Ltr)
- 35.1Mb
PDF (A4)
- 35.2Mb
Man Pages (TGZ)
- 256.4Kb
Man Pages (Zip)
- 361.2Kb
Info (Gzip)
- 3.4Mb
Info (Zip)
- 3.4Mb
Search Results
https://dev.mysql.com/doc/refman/5.7/en/replication-howto-masterstatus.html
Warning This procedure uses FLUSH TABLES WITH READ LOCK, which blocks COMMIT operations for InnoDB tables. To configure the replica to start the replication process at the correct point, you need to note the source's current coordinates within its ...
https://dev.mysql.com/doc/refman/5.7/en/replication-rbr-usage.html
For this reason, it is recommended that you use a transactional storage engine such as InnoDB for all tables replicated using the row-based format. MySQL uses statement-based logging (SBL), row-based logging (RBL) or mixed-format logging. The type ...
https://dev.mysql.com/doc/refman/5.7/en/replication-sbr-rbr.html
For InnoDB: An INSERT statement that uses AUTO_INCREMENT blocks other nonconflicting INSERT statements. For most users, the mixed replication format should provide the best combination of data integrity and performance. If, however, you want to take ...
https://dev.mysql.com/doc/refman/5.7/en/replication-solutions-diffengines.html
For example, in a typical scale-out scenario (see Section 16.3.4, “Using Replication for Scale-Out”), you want to use InnoDB tables on the source to take advantage of the transactional functionality, but use MyISAM on the replicas where ... It ...
https://dev.mysql.com/doc/refman/5.7/en/replication-solutions-partitioning.html
Note This does not work with InnoDB databases unless you use innodb_file_per_table. There may be situations where you have a single source and want to replicate different databases to different replicas. For example, you may want to distribute ...
https://dev.mysql.com/doc/refman/5.7/en/reproducible-test-case.html
For information about steps to take when encountering InnoDB table corruption, see Section 1.5, “How to Report Bugs or Problems”. If you encounter corrupted MyISAM tables or if mysqld always fails after some update statements, you can test ...
https://dev.mysql.com/doc/refman/5.7/en/reset-slave.html
From MySQL 5.7.24, when master_info_repository=TABLE is set on the server, replication connection parameters are preserved in the crash-safe InnoDB table mysql.slave_master_info as part of the RESET SLAVE operation. RESET SLAVE [ALL] ...
https://dev.mysql.com/doc/refman/5.7/en/select.html
(This does not occur with storage engines such as InnoDB that employ row-level locking.) For more information, see Section 22.6.4, “Partitioning and Locking”. SELECT [ALL | DISTINCT | DISTINCTROW ] [HIGH_PRIORITY] [STRAIGHT_JOIN] ...
https://dev.mysql.com/doc/refman/5.7/en/selinux-context-mysql-feature-ports.html
InnoDB Cluster relies on Group Replication so this applies equally to instances used in a cluster. If you enable certain MySQL features, you might need to set the SELinux TCP port context for additional ports used by those features. If ports used ...
https://dev.mysql.com/doc/refman/5.7/en/server-shutdown.html
InnoDB flushes its buffer pool to disk (unless innodb_fast_shutdown is 2), writes the current LSN to the tablespace, and terminates its own internal threads. The server shutdown process takes place as follows: The shutdown process is initiated. For ...