Search Results
Displaying 491 to 500
of 510 total results
- « Previous
- 48
- 49
- 50
- 51
- Next »
https://dev.mysql.com/doc/refman/8.4/en/programs-development.html
This section describes some utilities that you may find useful when developing MySQL programs. In shell scripts, you can use the my_print_defaults program to parse option files and see what options would be used by a given program. This works well ...
https://dev.mysql.com/doc/refman/8.4/en/replica-logs-status.html
A replica server creates two replication metadata repositories, the connection metadata repository and the applier metadata repository. If binary log file position based replication is in use, when the replica restarts, it reads the two ...
https://dev.mysql.com/doc/refman/8.4/en/replication-asynchronous-connection-failover-source.html
To activate asynchronous connection failover for a replication channel set SOURCE_CONNECTION_AUTO_FAILOVER=1 in a CHANGE REPLICATION SOURCE TO statement for this channel. GTID auto-positioning must be in use for the channel (SOURCE_AUTO_POSITION = ...Important When the existing connection to a source fails, the replica first retries the same connection the number of times specified by the SOURCE_RETRY_COUNT option of the CHANGE REPLICATION SOURCE ...
https://dev.mysql.com/doc/refman/8.4/en/replication-asynchronous-connection-failover.html
You can use the asynchronous connection failover mechanism to establish an asynchronous (source-to-replica) replication connection to a new source automatically, after the existing connection from a replica to its source fails. The asynchronous ...
https://dev.mysql.com/doc/refman/8.4/en/replication-features-transaction-inconsistencies.html
When GTID-based replication is in use (GTID_MODE=ON) and SOURCE_AUTO_POSITION is set for the replication channel using the CHANGE REPLICATION SOURCE TO statement, the old relay logs are not required for the recovery process. Instead, the replica can ... Inconsistencies in the sequence of transactions that have been executed from the relay log can occur depending on your replication ...
https://dev.mysql.com/doc/refman/8.4/en/replication-gtids-failover.html
GTIDs play a key role in applying changes to the database: the server automatically skips any transaction having an identifier which the server recognizes as one that it has processed before. This behavior is critical for automatic replication ...
https://dev.mysql.com/doc/refman/8.4/en/replication-gtids-functions.html
Provided that mysqldump was run with --set-gtid-purged set to ON or AUTO (the default), the output contains a SET @@GLOBAL.gtid_purged statement which adds the gtid_executed set from server2 to the gtid_purged set on server1. This section provides ...
https://dev.mysql.com/doc/refman/8.4/en/replication-howto-additionalslaves.html
After copying, delete the auto.cnf file from the copy of the data directory on the new replica, so that the new replica is started with a different generated server UUID. You can add another replica to an existing replication configuration without ...
https://dev.mysql.com/doc/refman/8.4/en/replication-mode-change-online-enable-gtids.html
This section describes how to enable GTID transactions, and optionally auto-positioning, on servers that are already online and using anonymous transactions. To start using the GTID protocol so that you can later perform automatic failover, execute ...This procedure does not require taking the server offline and is suited to use in ...
https://dev.mysql.com/doc/refman/8.4/en/restart.html
If auto-reconnect is enabled, the connection is reestablished after the server restarts. One use for RESTART is when it is not possible or convenient to gain command-line access to the MySQL server on the server host to restart it. For example, SET ...
Displaying 491 to 500
of 510 total results
- « Previous
- 48
- 49
- 50
- 51
- Next »