PDF (US Ltr)
- 35.1Mb
PDF (A4)
- 35.2Mb
Man Pages (TGZ)
- 255.8Kb
Man Pages (Zip)
- 360.7Kb
Info (Gzip)
- 3.4Mb
Info (Zip)
- 3.4Mb
Search Results
https://dev.mysql.com/doc/refman/5.7/en/binlog-replication-configuration-overview.html
This section describes replication between MySQL servers based on the binary log file position method, where the MySQL instance operating as the source (where the database changes originate) writes updates and changes as “events” to the binary ...
https://dev.mysql.com/doc/refman/5.7/en/replication-howto-masterstatus.html
To configure the replica to start the replication process at the correct point, you need to note the source's current coordinates within its binary log. Warning This procedure uses FLUSH TABLES WITH READ LOCK, which blocks COMMIT operations for ...
https://dev.mysql.com/doc/refman/5.7/en/replication-howto.html
This section describes how to set up a MySQL server to use binary log file position based replication. There are a number of different methods for setting up replication, and the exact method to use depends on how you are setting up replication, ...
https://dev.mysql.com/doc/refman/5.7/en/replication-options.html
The following 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 sources and replicas are covered separately, as are options and ...
21.7.9.1 NDB Cluster Replication: Automating Synchronization of the Replica to the Source Binary Log
https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-replication-auto-sync.html
It is possible to automate much of the process described in the previous section (see Section 21.7.9, “NDB Cluster Backups With NDB Cluster Replication”). The following Perl script reset-replica.pl serves as an example of how you can do this.
https://dev.mysql.com/doc/refman/5.7/en/replication-rules-db-options.html
When evaluating replication options, the replica begins by checking to see whether there are any --replicate-do-db or --replicate-ignore-db options that apply. When using --binlog-do-db or --binlog-ignore-db, the process is similar, but the options ...
https://dev.mysql.com/doc/refman/5.7/en/replication-multi-source-adding-binlog-master.html
These steps assume that you have enabled binary logging on the replication source server using --log-bin, the replica is using TABLE based replication metadata repositories, and that you have enabled a replication user and noted the current binary ...
https://dev.mysql.com/doc/refman/5.7/en/replication-rbr-safe-unsafe.html
The “safeness” of a statement in MySQL Replication, refers to whether the statement and its effects can be replicated correctly using statement-based format. If this is true of the statement, we refer to the statement as safe; otherwise, we ...
https://dev.mysql.com/doc/refman/5.7/en/binary-log-mysql-database.html
The contents of the grant tables in the mysql database can be modified directly (for example, with INSERT or DELETE) or indirectly (for example, with GRANT or CREATE USER). Statements that affect mysql database tables are written to the binary log ...
https://dev.mysql.com/doc/refman/5.7/en/replication-gtids-lifecycle.html
The life cycle of a GTID consists of the following steps: A transaction is executed and committed on the replication source server. This client transaction is assigned a GTID composed of the source's UUID and the smallest nonzero transaction ...