Search Results
https://dev.mysql.com/doc/refman/8.4/en/group-replication-responses-failure-expel.html
Consider increasing the value of group_replication_member_expel_timeout from the default in the following scenarios: The network is slow and the default 5 or 10 seconds before expulsion is not long enough for group members to always exchange at ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-single-primary-mode.html
The Group Replication flow control mechanism minimizes the difference between fast and slow members, and so reduces the chances of this happening if it is activated and properly tuned. In single-primary mode ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-status-variables.html
If this number grows over time, it means that at least one node is having problems answering to proposals, either due to something it to run slowly, or to network issues. This can be an indicator whether the group is making slow progress, or has ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-summary.html
Group Replication is an eventual consistency system, meaning that as soon as the incoming traffic slows down or stops, all group members have the same data content. Group Replication is a technique that can be used to implement fault-tolerant ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-understanding-consistency-guarantees.html
This means that as soon as the incoming traffic slows down or stops, all group members have the same data content. In terms of distributed consistency guarantees, either in normal or failure repair operations, Group Replication has always been an ...
https://dev.mysql.com/doc/refman/8.4/en/host-cache.html
The MySQL server maintains an in-memory host cache that contains information about clients: IP address, host name, and error information. The Performance Schema host_cache table exposes the contents of the host cache so that it can be examined ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-backup.html
Use the following procedure: Perform a slow shutdown of the MySQL server and make sure that it stops without errors. The key to safe database management is making regular backups. Hot and cold backups are physical backups that copy actual data ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-multi-versioning.html
If you insert and delete rows in smallish batches at about the same rate in the table, the purge thread can start to lag behind and the table can grow bigger and bigger because of all the “dead” rows, making everything disk-bound and very slow.
https://dev.mysql.com/doc/refman/8.4/en/memory-use.html
No memory overhead is needed for small items, thus avoiding the normal slow memory allocation and freeing. MySQL allocates buffers and caches to improve performance of database operations. The default configuration is designed to permit a MySQL ...
https://dev.mysql.com/doc/refman/8.4/en/myisamchk-check-options.html
myisamchk supports the following options for table checking operations: --check, -c Command-Line Format --check Check the table for errors. This is the default operation if you specify no option that selects an operation type explicitly.