PDF (US Ltr)
- 35.0Mb
PDF (A4)
- 35.1Mb
Man Pages (TGZ)
- 254.9Kb
Man Pages (Zip)
- 359.9Kb
Info (Gzip)
- 3.4Mb
Info (Zip)
- 3.4Mb
Search Results
https://dev.mysql.com/doc/refman/5.7/en/faqs-cjk.html
This set of Frequently Asked Questions derives from the experience of MySQL's Support and Development groups in handling many inquiries about CJK (Chinese-Japanese-Korean) issues. Where can I get help with CJK and related issues in MySQL? The ...
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/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-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/group-replication-primary-secondary-replication.html
Traditional MySQL Replication provides a simple Primary-Secondary approach to replication. There is a primary (source) and there are one or more secondaries (replicas). The primary executes transactions, commits them and then they are later (thus ...
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 ...
https://dev.mysql.com/doc/refman/5.7/en/group-replication-getting-started.html
MySQL Group Replication is provided as a plugin for the MySQL server; each server in a group requires configuration and installation of the plugin. This section provides a detailed tutorial with the steps required to create a replication group with ...In addition, InnoDB Cluster interfaces seamlessly with MySQL Router and simplifies deploying MySQL with high ...