MySQL :: MySQL 5.7 Reference Manual

Search Results

Displaying 61 to 70 of 78 total results

14.17.2 Monitoring InnoDB Mutex Waits Using Performance Schema

https://dev.mysql.com/doc/refman/5.7/en/monitor-innodb-mutex-waits-performance-schema.html

A mutex is a synchronization mechanism used in the code to enforce that only one thread at a given time can have access to a common resource. When two or more threads executing in the server need to access the same resource, the threads compete ...

15.2 The MyISAM Storage Engine

https://dev.mysql.com/doc/refman/5.7/en/myisam-storage-engine.html

MyISAM is based on the older (and no longer available) ISAM storage engine but has many useful extensions. Table 15.2 MyISAM Storage Engine Features Feature Support B-tree indexes Yes Backup/point-in-time recovery (Implemented in the server, rather ...

https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-config-starting.html

Changes in configuration are also likely to be indicated when changes are made in the platform on which the cluster is run, or in applications that use the NDB Cluster 's data. For these reasons, it is not possible to offer a single configuration ...

21.6.2.1 NDB Cluster: Messages in the Cluster Log

https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-logs-cluster-log.html

The following table lists the most common NDB cluster log messages. For information about the cluster log, log events, and event types, see Section 21.6.3, “Event Reports Generated in NDB Cluster”. These log messages also correspond to log ...

14.23 InnoDB Limits

https://dev.mysql.com/doc/refman/5.7/en/innodb-limits.html

This section describes limits for InnoDB tables, indexes, tablespaces, and other aspects of the InnoDB storage engine. A table can contain a maximum of 1017 columns (raised in MySQL 5.6.9 from the earlier limit of 1000). If innodb_large_prefix is ...

21.6.15.26 The ndbinfo memoryusage Table

https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndbinfo-memoryusage.html

Querying this table provides information similar to that provided by the ALL REPORT MemoryUsage command in the ndb_mgm client, or logged by ALL DUMP 1000. The memoryusage table contains the following columns: node_id The node ID of this data node.

14.8.8 Configuring InnoDB I/O Capacity

https://dev.mysql.com/doc/refman/5.7/en/innodb-configuring-io-capacity.html

The InnoDB master thread and other threads perform various tasks in the background, most of which are I/O related, such as flushing dirty pages from the buffer pool and writing changes from the change buffer to the appropriate secondary indexes.

21.5.6 ndb_blob_tool — Check and Repair BLOB and TEXT columns of NDB Cluster Tables

https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-programs-ndb-blob-tool.html

This tool can be used to check for and remove orphaned BLOB column parts from NDB tables, as well as to generate a file listing any orphaned parts. It is sometimes useful in diagnosing and repairing corrupted or damaged NDB tables containing BLOB ...

22.2.1 RANGE Partitioning

https://dev.mysql.com/doc/refman/5.7/en/partitioning-range.html

A table that is partitioned by range is partitioned in such a way that each partition contains rows for which the partitioning expression value lies within a given range. Ranges should be contiguous but not overlapping, and are defined using the ...

21.5.16 ndb_move_data — NDB Data Copy Utility

https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-programs-ndb-move-data.html

Usage The program is invoked with the names of the source and target tables; either or both of these may be qualified optionally with the database name. ndb_move_data options source target Options that can be used with ndb_move_data are shown in the ...

Displaying 61 to 70 of 78 total results