PDF (US Ltr)
- 43.3Mb
PDF (A4)
- 43.4Mb
Man Pages (TGZ)
- 296.6Kb
Man Pages (Zip)
- 402.0Kb
Info (Gzip)
- 4.3Mb
Info (Zip)
- 4.3Mb
Search Results
https://dev.mysql.com/doc/refman/8.0/en/replication-semisync.html
At this point, the transaction has committed on the source side, and receipt of its events has been acknowledged by at least one replica. As an alternative, you can configure the source so that the source waits for replica acknowledgment after ...
https://dev.mysql.com/doc/refman/8.0/en/replication-snapshot-method.html
Employing this method with a table using a storage engine that has complex caching or logging algorithms requires extra steps to produce a perfect “point in time” snapshot: the initial copy command could leave out cache information and logging ... If the source database contains existing data it is necessary to copy this data to each ...
https://dev.mysql.com/doc/refman/8.0/en/replication-solutions-backups-rawdata.html
Then you can use CHANGE REPLICATION SOURCE TO statement (from MySQL 8.0.23) or CHANGE MASTER TO statement (before MySQL 8.0.23) with the SOURCE_LOG_FILE | MASTER_LOG_FILE and SOURCE_LOG_POS | MASTER_LOG_POS options to tell the replica to re-read the ... To guarantee the integrity of the files that are copied, backing up the raw data files on your MySQL replica should take place while your replica server is shut ...
https://dev.mysql.com/doc/refman/8.0/en/replication-solutions-unexpected-replica-halt.html
Based on that position, the replication I/O thread (receiver) retrieves from the source's binary log all of the transactions that should be applied on the replica from that point on. In order for replication to be resilient to unexpected halts of ...
https://dev.mysql.com/doc/refman/8.0/en/replication-upgrade.html
Alternatively, if you cannot stop new statements, temporarily change to row-based logging on the source (binlog_format=ROW) and wait until all replicas have processed all binary logs produced up to the point of this change, then upgrade the replicas. When you upgrade servers that participate in a replication topology, you need to take into account each server's role in the topology and look out for issues specific to ...
https://dev.mysql.com/doc/refman/8.0/en/return.html
There may be more than one if the function has multiple exit points. RETURN expr The RETURN statement terminates execution of a stored function and returns the value expr to the function caller. There must be at least one RETURN statement in a ...
https://dev.mysql.com/doc/refman/8.0/en/server-shutdown.html
If the SQL thread is in the middle of a transaction at this point, the server waits until the current replication event group (if any) has finished executing, or until the user issues a KILL QUERY or KILL CONNECTION statement. The server shutdown ...
https://dev.mysql.com/doc/refman/8.0/en/server-status-variables.html
Handler_savepoint The number of requests for a storage engine to place a savepoint. Handler_savepoint_rollback The number of requests for a storage engine to roll back to a savepoint. Innodb_buffer_pool_load_status The progress of an operation to ...
https://dev.mysql.com/doc/refman/8.0/en/set-sql-log-bin.html
If you are using GTIDs for replication, this means that even when binary logging is later enabled again, the GTIDs written into the log from this point do not account for any transactions that occurred in the meantime, so in effect those ... SET ...
https://dev.mysql.com/doc/refman/8.0/en/show-replica-status.html
You can use this value with the CHANGE REPLICATION SOURCE TO statement's SOURCE_LOG_POS option (from MySQL 8.0.23) or the CHANGE MASTER TO statement's MASTER_LOG_POS option (before MySQL 8.0.23) when starting a new replica from an existing replica, ... SHOW {REPLICA | SLAVE} STATUS [FOR CHANNEL channel] This statement provides status information on essential parameters of the replica ...