Search Results
https://dev.mysql.com/doc/refman/8.4/en/group-replication-distributed-recovery-fault.html
Group Replication's distributed recovery process has a number of built-in measures to ensure fault tolerance in the event of any problems during the process. The donor for distributed recovery is selected randomly from the existing list of suitable ...
https://dev.mysql.com/doc/refman/8.4/en/group-replication-network-partitioning.html
The group needs to achieve consensus whenever a change that needs to be replicated happens. This is the case for regular transactions but is also required for group membership changes and some internal messaging that keeps the group consistent.
https://dev.mysql.com/doc/refman/8.4/en/handler.html
HANDLER tbl_name OPEN [ [AS] alias] HANDLER tbl_name READ index_name { = | <= | >= | < | > } (value1,value2,...) [ WHERE where_condition ] [LIMIT ... ] HANDLER tbl_name READ index_name { FIRST | NEXT | PREV | LAST } [ WHERE where_condition ] [LIMIT ...
https://dev.mysql.com/doc/refman/8.4/en/index-btree-hash.html
Understanding the B-tree and hash data structures can help predict how different queries perform on different storage engines that use these data structures in their indexes, particularly for the MEMORY storage engine that lets you choose B-tree or ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-and-mysql-replication.html
It is possible to use replication in a way where the storage engine on the replica is not the same as the storage engine on the source. For example, you can replicate modifications to an InnoDB table on the source to a MyISAM table on the replica.
https://dev.mysql.com/doc/refman/8.4/en/innodb-change-buffer.html
The change buffer is a special data structure that caches changes to secondary index pages when those pages are not in the buffer pool. The buffered changes, which may result from INSERT, UPDATE, or DELETE operations (DML), are merged later when ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-data-encryption.html
InnoDB supports data-at-rest encryption for file-per-table tablespaces, general tablespaces, the mysql system tablespace, redo logs, and undo logs. You can set an encryption default for schemas and general tablespaces; this permits DBAs to control ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-information-schema-fulltext_index-tables.html
INNODB_FT_BEING_DELETED: Provides a snapshot of the INNODB_FT_DELETED table; it is used only during an OPTIMIZE TABLE maintenance operation. When OPTIMIZE TABLE is run, the INNODB_FT_BEING_DELETED table is emptied, and DOC_ID values are removed from ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-locking.html
Shared and Exclusive Locks Intention Locks Record Locks Gap Locks Next-Key Locks Insert Intention Locks AUTO-INC Locks Predicate Locks for Spatial Indexes Shared and Exclusive Locks InnoDB implements standard row-level locking where there are two ...
https://dev.mysql.com/doc/refman/8.4/en/innodb-parameters.html
InnoDB Startup Options InnoDB System Variables System variables that are true or false can be enabled at server startup by naming them, or disabled by using a --skip- prefix. For example, to enable or disable the InnoDB adaptive hash index, you can ...