A number of types of statistical counters relating to actions performed by or affecting Ndb objects are available. Such actions include starting and closing (or aborting) transactions; primary key and unique key operations; table, range, and pruned scans; threads blocked while waiting for the completion of various operations; and data and events sent and received by NDBCLUSTER. The counters are incremented inside the NDB kernel whenever NDB API calls are made or data is sent to or received by the data nodes. mysqld exposes these counters as system status variables; their values can be read in the output of SHOW STATUS, or by querying the INFORMATION_SCHEMA.SESSION_STATUS or INFORMATION_SCHEMA.GLOBAL_STATUS table. By comparing the values before and after statements operating on NDB tables, you can observe the corresponding actions taken on the API level, and thus the cost of performing the statement.

You can list all of these status variables using the following SHOW STATUS statement:

mysql> SHOW STATUS LIKE 'ndb_api%';+--------------------------------------------+----------+| Variable_name                              | Value    |+--------------------------------------------+----------+| Ndb_api_wait_exec_complete_count_session   | 0        || Ndb_api_wait_scan_result_count_session     | 0        || Ndb_api_wait_meta_request_count_session    | 0        || Ndb_api_wait_nanos_count_session           | 0        || Ndb_api_bytes_sent_count_session           | 0        || Ndb_api_bytes_received_count_session       | 0        || Ndb_api_trans_start_count_session          | 0        || Ndb_api_trans_commit_count_session         | 0        || Ndb_api_trans_abort_count_session          | 0        || Ndb_api_trans_close_count_session          | 0        || Ndb_api_pk_op_count_session                | 0        || Ndb_api_uk_op_count_session                | 0        || Ndb_api_table_scan_count_session           | 0        || Ndb_api_range_scan_count_session           | 0        || Ndb_api_pruned_scan_count_session          | 0        || Ndb_api_scan_batch_count_session           | 0        || Ndb_api_read_row_count_session             | 0        || Ndb_api_trans_local_read_row_count_session | 0        || Ndb_api_event_data_count_injector          | 0        || Ndb_api_event_nondata_count_injector       | 0        || Ndb_api_event_bytes_count_injector         | 0        || Ndb_api_wait_exec_complete_count_slave     | 0        || Ndb_api_wait_scan_result_count_slave       | 0        || Ndb_api_wait_meta_request_count_slave      | 0        || Ndb_api_wait_nanos_count_slave             | 0        || Ndb_api_bytes_sent_count_slave             | 0        || Ndb_api_bytes_received_count_slave         | 0        || Ndb_api_trans_start_count_slave            | 0        || Ndb_api_trans_commit_count_slave           | 0        || Ndb_api_trans_abort_count_slave            | 0        || Ndb_api_trans_close_count_slave            | 0        || Ndb_api_pk_op_count_slave                  | 0        || Ndb_api_uk_op_count_slave                  | 0        || Ndb_api_table_scan_count_slave             | 0        || Ndb_api_range_scan_count_slave             | 0        || Ndb_api_pruned_scan_count_slave            | 0        || Ndb_api_scan_batch_count_slave             | 0        || Ndb_api_read_row_count_slave               | 0        || Ndb_api_trans_local_read_row_count_slave   | 0        || Ndb_api_wait_exec_complete_count           | 2        || Ndb_api_wait_scan_result_count             | 3        || Ndb_api_wait_meta_request_count            | 27       || Ndb_api_wait_nanos_count                   | 45612023 || Ndb_api_bytes_sent_count                   | 992      || Ndb_api_bytes_received_count               | 9640     || Ndb_api_trans_start_count                  | 2        || Ndb_api_trans_commit_count                 | 1        || Ndb_api_trans_abort_count                  | 0        || Ndb_api_trans_close_count                  | 2        || Ndb_api_pk_op_count                        | 1        || Ndb_api_uk_op_count                        | 0        || Ndb_api_table_scan_count                   | 1        || Ndb_api_range_scan_count                   | 0        || Ndb_api_pruned_scan_count                  | 0        || Ndb_api_scan_batch_count                   | 0        || Ndb_api_read_row_count                     | 1        || Ndb_api_trans_local_read_row_count         | 1        || Ndb_api_event_data_count                   | 0        || Ndb_api_event_nondata_count                | 0        || Ndb_api_event_bytes_count                  | 0        |+--------------------------------------------+----------+60 rows in set (0.02 sec)

These status variables are also available from the SESSION_STATUS and GLOBAL_STATUS tables of the INFORMATION_SCHEMA database, as shown here:

mysql> SELECT * FROM
        INFORMATION_SCHEMA.SESSION_STATUS     ->   WHERE
        VARIABLE_NAME LIKE 'ndb_api%';+--------------------------------------------+----------------+| VARIABLE_NAME                              | VARIABLE_VALUE |+--------------------------------------------+----------------+| NDB_API_WAIT_EXEC_COMPLETE_COUNT_SESSION   | 2              || NDB_API_WAIT_SCAN_RESULT_COUNT_SESSION     | 0              || NDB_API_WAIT_META_REQUEST_COUNT_SESSION    | 1              || NDB_API_WAIT_NANOS_COUNT_SESSION           | 8144375        || NDB_API_BYTES_SENT_COUNT_SESSION           | 68             || NDB_API_BYTES_RECEIVED_COUNT_SESSION       | 84             || NDB_API_TRANS_START_COUNT_SESSION          | 1              || NDB_API_TRANS_COMMIT_COUNT_SESSION         | 1              || NDB_API_TRANS_ABORT_COUNT_SESSION          | 0              || NDB_API_TRANS_CLOSE_COUNT_SESSION          | 1              || NDB_API_PK_OP_COUNT_SESSION                | 1              || NDB_API_UK_OP_COUNT_SESSION                | 0              || NDB_API_TABLE_SCAN_COUNT_SESSION           | 0              || NDB_API_RANGE_SCAN_COUNT_SESSION           | 0              || NDB_API_PRUNED_SCAN_COUNT_SESSION          | 0              || NDB_API_SCAN_BATCH_COUNT_SESSION           | 0              || NDB_API_READ_ROW_COUNT_SESSION             | 1              || NDB_API_TRANS_LOCAL_READ_ROW_COUNT_SESSION | 1              || NDB_API_EVENT_DATA_COUNT_INJECTOR          | 0              || NDB_API_EVENT_NONDATA_COUNT_INJECTOR       | 0              || NDB_API_EVENT_BYTES_COUNT_INJECTOR         | 0              || NDB_API_WAIT_EXEC_COMPLETE_COUNT_SLAVE     | 0              || NDB_API_WAIT_SCAN_RESULT_COUNT_SLAVE       | 0              || NDB_API_WAIT_META_REQUEST_COUNT_SLAVE      | 0              || NDB_API_WAIT_NANOS_COUNT_SLAVE             | 0              || NDB_API_BYTES_SENT_COUNT_SLAVE             | 0              || NDB_API_BYTES_RECEIVED_COUNT_SLAVE         | 0              || NDB_API_TRANS_START_COUNT_SLAVE            | 0              || NDB_API_TRANS_COMMIT_COUNT_SLAVE           | 0              || NDB_API_TRANS_ABORT_COUNT_SLAVE            | 0              || NDB_API_TRANS_CLOSE_COUNT_SLAVE            | 0              || NDB_API_PK_OP_COUNT_SLAVE                  | 0              || NDB_API_UK_OP_COUNT_SLAVE                  | 0              || NDB_API_TABLE_SCAN_COUNT_SLAVE             | 0              || NDB_API_RANGE_SCAN_COUNT_SLAVE             | 0              || NDB_API_PRUNED_SCAN_COUNT_SLAVE            | 0              || NDB_API_SCAN_BATCH_COUNT_SLAVE             | 0              || NDB_API_READ_ROW_COUNT_SLAVE               | 0              || NDB_API_TRANS_LOCAL_READ_ROW_COUNT_SLAVE   | 0              || NDB_API_WAIT_EXEC_COMPLETE_COUNT           | 4              || NDB_API_WAIT_SCAN_RESULT_COUNT             | 3              || NDB_API_WAIT_META_REQUEST_COUNT            | 28             || NDB_API_WAIT_NANOS_COUNT                   | 53756398       || NDB_API_BYTES_SENT_COUNT                   | 1060           || NDB_API_BYTES_RECEIVED_COUNT               | 9724           || NDB_API_TRANS_START_COUNT                  | 3              || NDB_API_TRANS_COMMIT_COUNT                 | 2              || NDB_API_TRANS_ABORT_COUNT                  | 0              || NDB_API_TRANS_CLOSE_COUNT                  | 3              || NDB_API_PK_OP_COUNT                        | 2              || NDB_API_UK_OP_COUNT                        | 0              || NDB_API_TABLE_SCAN_COUNT                   | 1              || NDB_API_RANGE_SCAN_COUNT                   | 0              || NDB_API_PRUNED_SCAN_COUNT                  | 0              || NDB_API_SCAN_BATCH_COUNT                   | 0              || NDB_API_READ_ROW_COUNT                     | 2              || NDB_API_TRANS_LOCAL_READ_ROW_COUNT         | 2              || NDB_API_EVENT_DATA_COUNT                   | 0              || NDB_API_EVENT_NONDATA_COUNT                | 0              || NDB_API_EVENT_BYTES_COUNT                  | 0              |+--------------------------------------------+----------------+60 rows in set (0.00 sec)mysql> SELECT * FROM INFORMATION_SCHEMA.GLOBAL_STATUS     ->     WHERE VARIABLE_NAME LIKE 'ndb_api%';+--------------------------------------------+----------------+| VARIABLE_NAME                              | VARIABLE_VALUE |+--------------------------------------------+----------------+| NDB_API_WAIT_EXEC_COMPLETE_COUNT_SESSION   | 2              || NDB_API_WAIT_SCAN_RESULT_COUNT_SESSION     | 0              || NDB_API_WAIT_META_REQUEST_COUNT_SESSION    | 1              || NDB_API_WAIT_NANOS_COUNT_SESSION           | 8144375        || NDB_API_BYTES_SENT_COUNT_SESSION           | 68             || NDB_API_BYTES_RECEIVED_COUNT_SESSION       | 84             || NDB_API_TRANS_START_COUNT_SESSION          | 1              || NDB_API_TRANS_COMMIT_COUNT_SESSION         | 1              || NDB_API_TRANS_ABORT_COUNT_SESSION          | 0              || NDB_API_TRANS_CLOSE_COUNT_SESSION          | 1              || NDB_API_PK_OP_COUNT_SESSION                | 1              || NDB_API_UK_OP_COUNT_SESSION                | 0              || NDB_API_TABLE_SCAN_COUNT_SESSION           | 0              || NDB_API_RANGE_SCAN_COUNT_SESSION           | 0              || NDB_API_PRUNED_SCAN_COUNT_SESSION          | 0              || NDB_API_SCAN_BATCH_COUNT_SESSION           | 0              || NDB_API_READ_ROW_COUNT_SESSION             | 1              || NDB_API_TRANS_LOCAL_READ_ROW_COUNT_SESSION | 1              || NDB_API_EVENT_DATA_COUNT_INJECTOR          | 0              || NDB_API_EVENT_NONDATA_COUNT_INJECTOR       | 0              || NDB_API_EVENT_BYTES_COUNT_INJECTOR         | 0              || NDB_API_WAIT_EXEC_COMPLETE_COUNT_SLAVE     | 0              || NDB_API_WAIT_SCAN_RESULT_COUNT_SLAVE       | 0              || NDB_API_WAIT_META_REQUEST_COUNT_SLAVE      | 0              || NDB_API_WAIT_NANOS_COUNT_SLAVE             | 0              || NDB_API_BYTES_SENT_COUNT_SLAVE             | 0              || NDB_API_BYTES_RECEIVED_COUNT_SLAVE         | 0              || NDB_API_TRANS_START_COUNT_SLAVE            | 0              || NDB_API_TRANS_COMMIT_COUNT_SLAVE           | 0              || NDB_API_TRANS_ABORT_COUNT_SLAVE            | 0              || NDB_API_TRANS_CLOSE_COUNT_SLAVE            | 0              || NDB_API_PK_OP_COUNT_SLAVE                  | 0              || NDB_API_UK_OP_COUNT_SLAVE                  | 0              || NDB_API_TABLE_SCAN_COUNT_SLAVE             | 0              || NDB_API_RANGE_SCAN_COUNT_SLAVE             | 0              || NDB_API_PRUNED_SCAN_COUNT_SLAVE            | 0              || NDB_API_SCAN_BATCH_COUNT_SLAVE             | 0              || NDB_API_READ_ROW_COUNT_SLAVE               | 0              || NDB_API_TRANS_LOCAL_READ_ROW_COUNT_SLAVE   | 0              || NDB_API_WAIT_EXEC_COMPLETE_COUNT           | 4              || NDB_API_WAIT_SCAN_RESULT_COUNT             | 3              || NDB_API_WAIT_META_REQUEST_COUNT            | 28             || NDB_API_WAIT_NANOS_COUNT                   | 53756398       || NDB_API_BYTES_SENT_COUNT                   | 1060           || NDB_API_BYTES_RECEIVED_COUNT               | 9724           || NDB_API_TRANS_START_COUNT                  | 3              || NDB_API_TRANS_COMMIT_COUNT                 | 2              || NDB_API_TRANS_ABORT_COUNT                  | 0              || NDB_API_TRANS_CLOSE_COUNT                  | 3              || NDB_API_PK_OP_COUNT                        | 2              || NDB_API_UK_OP_COUNT                        | 0              || NDB_API_TABLE_SCAN_COUNT                   | 1              || NDB_API_RANGE_SCAN_COUNT                   | 0              || NDB_API_PRUNED_SCAN_COUNT                  | 0              || NDB_API_SCAN_BATCH_COUNT                   | 0              || NDB_API_READ_ROW_COUNT                     | 2              || NDB_API_TRANS_LOCAL_READ_ROW_COUNT         | 2              || NDB_API_EVENT_DATA_COUNT                   | 0              || NDB_API_EVENT_NONDATA_COUNT                | 0              || NDB_API_EVENT_BYTES_COUNT                  | 0              |+--------------------------------------------+----------------+60 rows in set (0.00 sec)

Each Ndb object has its own counters. NDB API applications can read the values of the counters for use in optimization or monitoring. For multithreaded clients which use more than one Ndb object concurrently, it is also possible to obtain a summed view of counters from all Ndb objects belonging to a given Ndb_cluster_connection.

Four sets of these counters are exposed. One set applies to the current session only; the other 3 are global. This is in spite of the fact that their values can be obtained as either session or global status variables in the mysql client. This means that specifying the SESSION or GLOBAL keyword with SHOW STATUS has no effect on the values reported for NDB API statistics status variables, and the value for each of these variables is the same whether the value is obtained from the equivalent column of the SESSION_STATUS or the GLOBAL_STATUS table.

You can obtain values for a particular set of variables by additionally filtering for the substring session, slave, or injector in the variable name (along with the common prefix Ndb_api). For _session variables, this can be done as shown here:

mysql> SHOW STATUS LIKE
        'ndb_api%session';+--------------------------------------------+---------+| Variable_name                              | Value   |+--------------------------------------------+---------+| Ndb_api_wait_exec_complete_count_session   | 2       || Ndb_api_wait_scan_result_count_session     | 0       || Ndb_api_wait_meta_request_count_session    | 1       || Ndb_api_wait_nanos_count_session           | 8144375 || Ndb_api_bytes_sent_count_session           | 68      || Ndb_api_bytes_received_count_session       | 84      || Ndb_api_trans_start_count_session          | 1       || Ndb_api_trans_commit_count_session         | 1       || Ndb_api_trans_abort_count_session          | 0       || Ndb_api_trans_close_count_session          | 1       || Ndb_api_pk_op_count_session                | 1       || Ndb_api_uk_op_count_session                | 0       || Ndb_api_table_scan_count_session           | 0       || Ndb_api_range_scan_count_session           | 0       || Ndb_api_pruned_scan_count_session          | 0       || Ndb_api_scan_batch_count_session           | 0       || Ndb_api_read_row_count_session             | 1       || Ndb_api_trans_local_read_row_count_session | 1       |+--------------------------------------------+---------+18 rows in set (0.50 sec)

To obtain a listing of the NDB API mysqld-level status variables, filter for variable names beginning with ndb_api and ending in _count, like this:

mysql> SELECT * FROM
        INFORMATION_SCHEMA.SESSION_STATUS     ->     WHERE
        VARIABLE_NAME LIKE 'ndb_api%count';+------------------------------------+----------------+| VARIABLE_NAME                      | VARIABLE_VALUE |+------------------------------------+----------------+| NDB_API_WAIT_EXEC_COMPLETE_COUNT   | 4              || NDB_API_WAIT_SCAN_RESULT_COUNT     | 3              || NDB_API_WAIT_META_REQUEST_COUNT    | 28             || NDB_API_WAIT_NANOS_COUNT           | 53756398       || NDB_API_BYTES_SENT_COUNT           | 1060           || NDB_API_BYTES_RECEIVED_COUNT       | 9724           || NDB_API_TRANS_START_COUNT          | 3              || NDB_API_TRANS_COMMIT_COUNT         | 2              || NDB_API_TRANS_ABORT_COUNT          | 0              || NDB_API_TRANS_CLOSE_COUNT          | 3              || NDB_API_PK_OP_COUNT                | 2              || NDB_API_UK_OP_COUNT                | 0              || NDB_API_TABLE_SCAN_COUNT           | 1              || NDB_API_RANGE_SCAN_COUNT           | 0              || NDB_API_PRUNED_SCAN_COUNT          | 0              || NDB_API_SCAN_BATCH_COUNT           | 0              || NDB_API_READ_ROW_COUNT             | 2              || NDB_API_TRANS_LOCAL_READ_ROW_COUNT | 2              || NDB_API_EVENT_DATA_COUNT           | 0              || NDB_API_EVENT_NONDATA_COUNT        | 0              || NDB_API_EVENT_BYTES_COUNT          | 0              |+------------------------------------+----------------+21 rows in set (0.09 sec)

Not all counters are reflected in all 4 sets of status variables. For the event counters DataEventsRecvdCount, NondataEventsRecvdCount, and EventBytesRecvdCount, only _injector and mysqld-level NDB API status variables are available:

mysql> SHOW STATUS LIKE
        'ndb_api%event%';+--------------------------------------+-------+| Variable_name                        | Value |+--------------------------------------+-------+| Ndb_api_event_data_count_injector    | 0     || Ndb_api_event_nondata_count_injector | 0     || Ndb_api_event_bytes_count_injector   | 0     || Ndb_api_event_data_count             | 0     || Ndb_api_event_nondata_count          | 0     || Ndb_api_event_bytes_count            | 0     |+--------------------------------------+-------+6 rows in set (0.00 sec)

_injector status variables are not implemented for any other NDB API counters, as shown here:

mysql> SHOW STATUS LIKE
        'ndb_api%injector%';+--------------------------------------+-------+| Variable_name                        | Value |+--------------------------------------+-------+| Ndb_api_event_data_count_injector    | 0     || Ndb_api_event_nondata_count_injector | 0     || Ndb_api_event_bytes_count_injector   | 0     |+--------------------------------------+-------+3 rows in set (0.00 sec)

The names of the status variables can easily be associated with the names of the corresponding counters. Each NDB API statistics counter is listed in the following table with a description as well as the names of any MySQL server status variables corresponding to this counter.

To see all counts of committed transactions—that is, all TransCommitCount counter status variables—you can filter the results of SHOW STATUS for the substring trans_commit_count, like this:

mysql> SHOW STATUS LIKE
        '%trans_commit_count%';+------------------------------------+-------+| Variable_name                      | Value |+------------------------------------+-------+| Ndb_api_trans_commit_count_session | 1     || Ndb_api_trans_commit_count_slave   | 0     || Ndb_api_trans_commit_count         | 2     |+------------------------------------+-------+3 rows in set (0.00 sec)

From this you can determine that 1 transaction has been committed in the current mysql client session, and 2 transactions have been committed on this mysqld since it was last restarted.

You can see how various NDB API counters are incremented by a given SQL statement by comparing the values of the corresponding _session status variables immediately before and after performing the statement. In this example, after getting the initial values from SHOW STATUS, we create in the test database an NDB table, named t, that has a single column:

mysql> SHOW STATUS LIKE
        'ndb_api%session%';+--------------------------------------------+--------+| Variable_name                              | Value  |+--------------------------------------------+--------+| Ndb_api_wait_exec_complete_count_session   | 2      || Ndb_api_wait_scan_result_count_session     | 0      || Ndb_api_wait_meta_request_count_session    | 3      || Ndb_api_wait_nanos_count_session           | 820705 || Ndb_api_bytes_sent_count_session           | 132    || Ndb_api_bytes_received_count_session       | 372    || Ndb_api_trans_start_count_session          | 1      || Ndb_api_trans_commit_count_session         | 1      || Ndb_api_trans_abort_count_session          | 0      || Ndb_api_trans_close_count_session          | 1      || Ndb_api_pk_op_count_session                | 1      || Ndb_api_uk_op_count_session                | 0      || Ndb_api_table_scan_count_session           | 0      || Ndb_api_range_scan_count_session           | 0      || Ndb_api_pruned_scan_count_session          | 0      || Ndb_api_scan_batch_count_session           | 0      || Ndb_api_read_row_count_session             | 1      || Ndb_api_trans_local_read_row_count_session | 1      |+--------------------------------------------+--------+18 rows in set (0.00 sec)mysql> USE test;Database changedmysql> CREATE
        TABLE t (c INT) ENGINE NDBCLUSTER;Query OK, 0 rows affected (0.85 sec)

Now you can execute a new SHOW STATUS statement and observe the changes, as shown here (with the changed rows highlighted in the output):

mysql> SHOW STATUS LIKE 'ndb_api%session%';+--------------------------------------------+-----------+| Variable_name                              | Value     |+--------------------------------------------+-----------+| Ndb_api_wait_exec_complete_count_session | 8 || Ndb_api_wait_scan_result_count_session     | 0         || Ndb_api_wait_meta_request_count_session | 17 ||
        Ndb_api_wait_nanos_count_session | 706871709 ||
        Ndb_api_bytes_sent_count_session | 2376 ||
        Ndb_api_bytes_received_count_session | 3844 ||
        Ndb_api_trans_start_count_session | 4 ||
        Ndb_api_trans_commit_count_session | 4
        || Ndb_api_trans_abort_count_session          | 0         ||
        Ndb_api_trans_close_count_session | 4 || Ndb_api_pk_op_count_session | 6
        || Ndb_api_uk_op_count_session                | 0         || Ndb_api_table_scan_count_session           | 0         || Ndb_api_range_scan_count_session           | 0         || Ndb_api_pruned_scan_count_session          | 0         || Ndb_api_scan_batch_count_session           | 0         || Ndb_api_read_row_count_session | 2 || Ndb_api_trans_local_read_row_count_session | 1         |+--------------------------------------------+-----------+18 rows in set (0.00 sec)

Similarly, you can see the changes in the NDB API statistics counters caused by inserting a row into t: Insert the row, then run the same SHOW STATUS statement used in the previous example, as shown here:

mysql> INSERT INTO t VALUES (100);Query OK, 1 row affected (0.00 sec)mysql> SHOW STATUS LIKE 'ndb_api%session%';+--------------------------------------------+-----------+| Variable_name                              | Value     |+--------------------------------------------+-----------+| Ndb_api_wait_exec_complete_count_session | 11 || Ndb_api_wait_scan_result_count_session | 6 ||
        Ndb_api_wait_meta_request_count_session | 20 ||
        Ndb_api_wait_nanos_count_session | 707370418 ||
        Ndb_api_bytes_sent_count_session | 2724 ||
        Ndb_api_bytes_received_count_session | 4116 ||
        Ndb_api_trans_start_count_session | 7 ||
        Ndb_api_trans_commit_count_session | 6
        || Ndb_api_trans_abort_count_session          | 0         ||
        Ndb_api_trans_close_count_session | 7 || Ndb_api_pk_op_count_session | 8
        || Ndb_api_uk_op_count_session                | 0         ||
        Ndb_api_table_scan_count_session | 1 || Ndb_api_range_scan_count_session           | 0         || Ndb_api_pruned_scan_count_session          | 0         || Ndb_api_scan_batch_count_session           | 0         || Ndb_api_read_row_count_session | 3 ||
        Ndb_api_trans_local_read_row_count_session | 2 |+--------------------------------------------+-----------+18 rows in set (0.00 sec)

We can make a number of observations from these results: