Search Results
https://dev.mysql.com/doc/refman/8.4/en/pluggable-authentication.html
Windows native authentication: Connecting through an account that uses the Windows plugin requires Windows Domain setup. When a client connects to the MySQL server, the server uses the user name provided by the client and the client host to select ...
https://dev.mysql.com/doc/refman/8.4/en/problems-connecting.html
If you encounter problems when you try to connect to the MySQL server, the following items describe some courses of action you can take to correct the problem. To correct this when you invoke a client program, specify a --port option to indicate ...
https://dev.mysql.com/doc/refman/8.4/en/programs-overview.html
Several programs perform setup operations during MySQL installation or upgrading: comp_err This program is used during the MySQL build/installation process. Later sections provide a more detailed description of each one, with the exception of NDB ...
https://dev.mysql.com/doc/refman/8.4/en/replication-channels.html
For GTID-based replication, if the same transaction might arrive from multiple sources (such as in a diamond topology), you must ensure the filtering setup is the same on all channels. In MySQL multi-source replication, a replica opens multiple ...
https://dev.mysql.com/doc/refman/8.4/en/replication-configuration.html
This section describes how to configure the different types of replication available in MySQL and includes the setup and configuration required for a replication environment, including step-by-step instructions for creating a new replication ...For ...
https://dev.mysql.com/doc/refman/8.4/en/replication-features-shutdowns.html
For the greatest possible durability and consistency in a replication setup using InnoDB with transactions, you should also set innodb_flush_log_at_trx_commit=1. It is safe to shut down a replication source server and restart it later. When a ...
https://dev.mysql.com/doc/refman/8.4/en/replication-gtids-failover.html
When restoring a replica in a GTID based replication setup that has encountered an error, injecting an empty transaction may not solve the problem because an event does not have a GTID. There are a number of techniques when using MySQL Replication ...
https://dev.mysql.com/doc/refman/8.4/en/replication-gtids-lifecycle.html
You might need to do this after carrying out test queries to verify a replication setup on new GTID-enabled servers, or when you want to join a new server to a replication group but it contains some unwanted local transactions that are not accepted ... The life cycle of a GTID consists of the following steps: A transaction is executed and committed on the ...
https://dev.mysql.com/doc/refman/8.4/en/replication-howto-masterbaseconfig.html
Note The following options also have an impact on the source: For the greatest possible durability and consistency in a replication setup using InnoDB with transactions, you should use innodb_flush_log_at_trx_commit=1 and sync_binlog=1 in the ... To ...
https://dev.mysql.com/doc/refman/8.4/en/replication-multi-source.html
For GTID-based replication, if the same transaction might arrive from multiple sources (such as in a diamond topology), you must ensure the filtering setup is the same on all channels. Multi-source replication in MySQL 8.4 enables a replica to ...