NDB API Statistics Counters and Variables +--------------------------------------+-------+ | 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 | +--------------------------------------+-------+ +--------------------------------------+-------+ | Variable_name | Value | +--------------------------------------+-------+ | Ndb_api_event_data_count_injector | 0 | | Ndb_api_event_nondata_count_injector | 0 | | Ndb_api_event_bytes_count_injector | 0 | +--------------------------------------+-------+ Counter Name Description Status Variables (by statistic type): •Session •Slave (replica) •Injector •Server WaitExecCompleteCount Number of times thread has been blocked while waiting for execution of an operation to complete. Includes all  execute() calls as well as implicit executes for blob operations and auto- increment not visible to clients. • • •[none] • Ndb_api_wait_exec_complete_count WaitScanResultCount Number of times thread has been blocked while waiting for a scan- based signal, such waiting for additional results, or for a scan to close. • • •[none] • Ndb_api_wait_scan_result_count WaitMetaRequestCount Number of times thread has been blocked waiting for a metadata- based signal; this can occur when • • 4514 6 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. Table 23.66 NDB API statistics counters _injector  status variables are not implemented for any other NDB API counters, as shown here: 3 rows in set (0.00 sec) mysql>  SHOW STATUS LIKE ’ndb_api%injector%’;