Syntax:
SHOW ENGINE engine_name {STATUS | MUTEX}

SHOW ENGINE displays operational information about a storage engine. It
requires the PROCESS privilege. The statement has these variants:

SHOW ENGINE INNODB STATUS
SHOW ENGINE INNODB MUTEX
SHOW ENGINE PERFORMANCE_SCHEMA STATUS

SHOW ENGINE INNODB STATUS displays extensive information from the
standard InnoDB Monitor about the state of the InnoDB storage engine.
For information about the standard monitor and other InnoDB Monitors
that provide information about InnoDB processing, see
http://dev.mysql.com/doc/refman/5.7/en/innodb-monitors.html.

SHOW ENGINE INNODB MUTEX displays InnoDB mutex and rw-lock statistics.

*Note*:

InnoDB mutexes and rwlocks can also be monitored using Performance
Schema tables. See
http://dev.mysql.com/doc/refman/5.7/en/monitor-innodb-mutex-waits-perfo
rmance-schema.html.

SHOW ENGINE INNODB MUTEX output was removed in MySQL 5.7.2. It was
revised and reintroduced in MySQL 5.7.8.

In MySQL 5.7.8, mutex statistics collection is configured dynamically
using the following options:

o To enable the collection of mutex statistics, run:

SET GLOBAL innodb_monitor_enable='latch';

o To reset mutex statistics, run:

SET GLOBAL innodb_monitor_reset='latch';

o To disable the collection of mutex statistics, run:

SET GLOBAL innodb_monitor_disable='latch';

Collection of mutex statistics for SHOW ENGINE INNODB MUTEX can also be
enabled by setting innodb_monitor_enable='all', or disabled by setting
innodb_monitor_disable='all'.

SHOW ENGINE INNODB MUTEX output has the following columns:

o Type

  Always InnoDB.

o Name

  Prior to MySQL 5.7.8, the Name field reports the source file where
  the mutex is implemented, and the line number in the file where the
  mutex is created. The line number is specific to your version of
  MySQL. As of MySQL 5.7.8, only the mutex name is reported. File name
  and line number are still reported for rwlocks.

o Status

  The mutex status.

  Prior to MySQL 5.7.8, the Status field displays several values if
  WITH_DEBUG was defined at MySQL compilation time. If WITH_DEBUG was
  not defined, the statement displays only the os_waits value. In the
  latter case (without WITH_DEBUG), the information on which the output
  is based is insufficient to distinguish regular mutexes and mutexes
  that protect rwlocks (which permit multiple readers or a single
  writer). Consequently, the output may appear to contain multiple rows
  for the same mutex. Pre-MySQL 5.7.8 Status field values include:

  o count indicates how many times the mutex was requested.

  o spin_waits indicates how many times the spinlock had to run.

  o spin_rounds indicates the number of spinlock rounds. (spin_rounds
    divided by spin_waits provides the average round count.)

  o os_waits indicates the number of operating system waits. This
    occurs when the spinlock did not work (the mutex was not locked
    during the spinlock and it was necessary to yield to the operating
    system and wait).

  o os_yields indicates the number of times a thread trying to lock a
    mutex gave up its timeslice and yielded to the operating system (on
    the presumption that permitting other threads to run will free the
    mutex so that it can be locked).

  o os_wait_times indicates the amount of time (in ms) spent in
    operating system waits. In MySQL 5.7 timing is disabled and this
    value is always 0.

  As of MySQL 5.7.8, the Status field reports the number of spins,
  waits, and calls. Statistics for low-level operating system mutexes,
  which are implemented outside of InnoDB, are not reported.

  o spins indicates the number of spins.

  o waits indicates the number of mutex waits.

  o calls indicates how many times the mutex was requested.

SHOW ENGINE INNODB MUTEX skips the mutexes and rw-locks of buffer pool
blocks, as the amount of output can be overwhelming on systems with a
large buffer pool. (There is one mutex and one rw-lock in each 16K
buffer pool block, and there are 65,536 blocks per gigabyte.) SHOW
ENGINE INNODB MUTEX also does not list any mutexes or rw-locks that
have never been waited on (os_waits=0). Thus, SHOW ENGINE INNODB MUTEX
only displays information about mutexes and rw-locks outside of the
buffer pool that have caused at least one OS-level wait.

Use SHOW ENGINE PERFORMANCE_SCHEMA STATUS to inspect the internal
operation of the Performance Schema code:

mysql> SHOW ENGINE PERFORMANCE_SCHEMA STATUS\G
...
*************************** 3. row ***************************
  Type: performance_schema
  Name: events_waits_history.size
Status: 76
*************************** 4. row ***************************
  Type: performance_schema
  Name: events_waits_history.count
Status: 10000
*************************** 5. row ***************************
  Type: performance_schema
  Name: events_waits_history.memory
Status: 760000
...
*************************** 57. row ***************************
  Type: performance_schema
  Name: performance_schema.memory
Status: 26459600
...

This statement is intended to help the DBA understand the effects that
different Performance Schema options have on memory requirements.

Name values consist of two parts, which name an internal buffer and a
buffer attribute, respectively. Interpret buffer names as follows:

o An internal buffer that is not exposed as a table is named within
  parentheses. Examples: (pfs_cond_class).size,
  (pfs_mutex_class).memory.

o An internal buffer that is exposed as a table in the
  performance_schema database is named after the table, without
  parentheses. Examples: events_waits_history.size,
  mutex_instances.count.

o A value that applies to the Performance Schema as a whole begins with
  performance_schema. Example: performance_schema.memory.

Buffer attributes have these meanings:

o size is the size of the internal record used by the implementation,
  such as the size of a row in a table. size values cannot be changed.

o count is the number of internal records, such as the number of rows
  in a table. count values can be changed using Performance Schema
  configuration options.

o For a table, tbl_name.memory is the product of size and count. For
  the Performance Schema as a whole, performance_schema.memory is the
  sum of all the memory used (the sum of all other memory values).

In some cases, there is a direct relationship between a Performance
Schema configuration parameter and a SHOW ENGINE value. For example,
events_waits_history_long.count corresponds to
performance_schema_events_waits_history_long_size. In other cases, the
relationship is more complex. For example, events_waits_history.count
corresponds to performance_schema_events_waits_history_size (the number
of rows per thread) multiplied by
performance_schema_max_thread_instances ( the number of threads).

SHOW ENGINE NDB STATUS If the server has the NDB storage engine
enabled, SHOW ENGINE NDB STATUS displays cluster status information
such as the number of connected data nodes, the cluster connectstring,
and cluster binary log epochs, as well as counts of various Cluster API
objects created by the MySQL Server when connected to the cluster.
Sample output from this statement is shown here:

mysql> SHOW ENGINE NDB STATUS;
+------------+-----------------------+--------------------------------------------------+
| Type       | Name                  | Status                                           |
+------------+-----------------------+--------------------------------------------------+
| ndbcluster | connection            | cluster_node_id=7,
  connected_host=192.168.0.103, connected_port=1186, number_of_data_nodes=4,
  number_of_ready_data_nodes=3, connect_count=0                                         |
| ndbcluster | NdbTransaction        | created=6, free=0, sizeof=212                    |
| ndbcluster | NdbOperation          | created=8, free=8, sizeof=660                    |
| ndbcluster | NdbIndexScanOperation | created=1, free=1, sizeof=744                    |
| ndbcluster | NdbIndexOperation     | created=0, free=0, sizeof=664                    |
| ndbcluster | NdbRecAttr            | created=1285, free=1285, sizeof=60               |
| ndbcluster | NdbApiSignal          | created=16, free=16, sizeof=136                  |
| ndbcluster | NdbLabel              | created=0, free=0, sizeof=196                    |
| ndbcluster | NdbBranch             | created=0, free=0, sizeof=24                     |
| ndbcluster | NdbSubroutine         | created=0, free=0, sizeof=68                     |
| ndbcluster | NdbCall               | created=0, free=0, sizeof=16                     |
| ndbcluster | NdbBlob               | created=1, free=1, sizeof=264                    |
| ndbcluster | NdbReceiver           | created=4, free=0, sizeof=68                     |
| ndbcluster | binlog                | latest_epoch=155467, latest_trans_epoch=148126,
  latest_received_binlog_epoch=0, latest_handled_binlog_epoch=0,
  latest_applied_binlog_epoch=0                                                         |
+------------+-----------------------+--------------------------------------------------+

The Status column in each of these rows provides information about the
MySQL server's connection to the cluster and about the cluster binary
log's status, respectively. The Status information is in the form of
comma-delimited set of name/value pairs.

URL: http://dev.mysql.com/doc/refman/5.7/en/show-engine.html

