PDF (US Ltr)
- 35.1Mb
PDF (A4)
- 35.2Mb
Man Pages (TGZ)
- 255.8Kb
Man Pages (Zip)
- 360.8Kb
Info (Gzip)
- 3.4Mb
Info (Zip)
- 3.4Mb
Search Results
https://dev.mysql.com/doc/refman/5.7/en/group-replication-data-manipulation-statements.html
As there are no primary servers (sources) for any particular data set, every server in the group is allowed to execute transactions at any time, even transactions that change state (RW transactions). But, at commit time, it coordinates with the ...
https://dev.mysql.com/doc/refman/5.7/en/innodb-persistent-stats.html
For example, the following query retrieves index sizes for partitions of table t1: mysql> SELECT SUM(stat_value) pages, index_name, SUM(stat_value)*@@innodb_page_size size FROM mysql.innodb_index_stats WHERE table_name like 't1#P%' AND stat_name = ... The persistent optimizer statistics feature improves plan stability by storing statistics to disk and making them persistent across server restarts so that the optimizer is more likely to make consistent choices each time for a given ...
https://dev.mysql.com/doc/refman/5.7/en/group-replication-observability.html
There is a lot of automation built into the Group Replication plugin. This is where the instrumentation of Group Replication and Performance Schema becomes important. The distributed nature of the replication protocol and the fact that server ...
https://dev.mysql.com/doc/refman/5.7/en/firewall-usage.html
The benefit of statement normalization is that it enables similar statements to be grouped and recognized using a single pattern. Before using MySQL Enterprise Firewall, install it according to the instructions provided in Section 6.4.6.2, ...
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-replication-group-members-table.html
This table shows network and status information for replication group members. The network addresses shown are the addresses used to connect clients to the group, and should not be confused with the member's internal group communication address ...
https://dev.mysql.com/doc/refman/5.7/en/stop-group-replication.html
As soon as you issue STOP GROUP_REPLICATION the member is set to super_read_only=ON, which ensures that no writes can be made to the member while Group Replication stops. Warning Use this statement with extreme caution because it removes the server ...Any other replication channels running on the member are also ...
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-replication-group-member-stats-table.html
This table shows statistical information for MySQL Group Replication members. The replication_group_member_stats table has these columns: CHANNEL_NAME Name of the Group Replication channel. This has a different value for each member in the group.
https://dev.mysql.com/doc/refman/5.7/en/group-replication-distributed-recovery.html
This section describes the process through which a member joining a group catches up with the remaining servers in the group, called distributed recovery. Distributed recovery can be summarized as the process through which a server gets missing ...
https://dev.mysql.com/doc/refman/5.7/en/group-replication-examples-of-use-case-scenarios.html
The following examples are typical use cases for Group Replication. Use MySQL Group Replication to implement highly available shards, where each shard maps to a replication group. Writing to an entire group may prove more scalable under certain ...
https://dev.mysql.com/doc/refman/5.7/en/group-replication-fault-tolerance.html
MySQL Group Replication builds on an implementation of the Paxos distributed algorithm to provide distributed coordination between servers. In practice this means that to tolerate one failure the group must have three servers in it. However, if a ...As such, it requires a majority of servers to be active to reach quorum and thus make a ...