Search Results
https://dev.mysql.com/doc/refman/8.4/en/explain-output.html
The EXPLAIN statement provides information about how MySQL executes statements. It lists the tables in the output in the order that MySQL would read them while processing the statement. This means that MySQL reads a row from the first table, then ...EXPLAIN returns a row of information for each table used in the SELECT ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-fault-tolerance.html
MySQL Group Replication builds on an implementation of the Paxos distributed algorithm to provide distributed coordination between servers. As such, it requires a majority of servers to be active to reach quorum and thus make a decision. This has ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-message-compression.html
Compression for messages sent in the group happens at the group communication engine level, before the data is handed over to the group communication thread, so it takes place within the context of the mysql user session thread. For messages sent ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-network-partitioning.html
mysql> SELECT @@group_replication_local_address; Once you know the group communication addresses of s1 (127.0.0.1:10000) and s2 (127.0.0.1:10001), you can use that on one of the two servers to inject a new membership configuration, thus overriding ... The group needs to achieve consensus whenever a change that needs to be replicated ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-single-primary-mode.html
Each member makes its own decision locally, following the primary election algorithm in its MySQL Server release. Because all members must reach the same decision, members adapt their primary election algorithm if other group members are running ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-summary.html
MySQL Group Replication builds on top of such properties and abstractions and implements a multi-source update everywhere replication protocol. The following figure depicts the MySQL Group Replication protocol and by comparing it to MySQL ... Group ...
https://dev.mysql.com/doc/refman/8.4/en/known-issues.html
This section lists known issues in recent versions of MySQL. For information about platform-specific issues, see the installation and debugging instructions in Section 2.1, “General Installation Guidance”, and Section 7.9, “Debugging MySQL”. Even if you use lower_case_table_names=2 (which enables MySQL to remember the case used for databases and table names), MySQL does not remember the case used for database names for the function DATABASE() or within the various logs (on case-insensitive ...
https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-replication.html
We assume some familiarity on the part of the reader with standard MySQL replication as discussed elsewhere in this Manual. This process is accomplished by a special thread known as the NDB binary log injector thread, which runs on each MySQL server ... NDB Cluster supports asynchronous replication, more usually referred to simply as ...
https://dev.mysql.com/doc/refman/8.4/en/optimizing-innodb-storage-layout.html
Once your data reaches a stable size, or a growing table has increased by tens or some hundreds of megabytes, consider using the OPTIMIZE TABLE statement to reorganize the table and compact any wasted space. The reorganized tables require less disk ...
https://dev.mysql.com/doc/refman/8.4/en/optimizing-innodb-transaction-management.html
The default MySQL setting AUTOCOMMIT=1 can impose performance limitations on a busy database server. To optimize InnoDB transaction processing, find the ideal balance between the performance overhead of transactional features and the workload of ...