content_image/800454.jpg
| cluster_transactions | | config_nodes | | config_params | | config_values | | counters | | cpustat | | cpustat_1sec | | cpustat_20sec | | cpustat_50ms | | dict_obj_info | | dict_obj_types | | disk_write_speed_aggregate | | disk_write_speed_aggregate_node | | disk_write_speed_base | | diskpagebuffer | | error_messages | | locks_per_fragment | | logbuffers | | logspaces | | membership | | memory_per_fragment | | memoryusage | | nodes | | operations_per_fragment | | processes | | resources | | restart_info | | server_locks | | server_operations | | server_transactions | | table_distribution_status | | table_fragments | | table_info | | table_replicas | | tc_time_track_stats | | threadblocks | | threads | | threadstat | | transporters | +---------------------------------+ 44 rows in set (0.00 sec) 

In NDB 8.0, all ndbinfo  tables use the NDB  storage engine; however, an ndbinfo  entry still appears in the output of SHOW ENGINES  and SHOW PLUGINS  as described previously. 

You can execute SELECT  statements against these tables, just as you would normally expect: 

mysql> SELECT * FROM memoryusage; 

<img src='content_image/800454.jpg'>

6 rows in set (0.02 sec) 

More complex queries, such as the two following SELECT  statements using the memoryusage  table, are possible: 

mysql> SELECT SUM(used) as ’Data Memory Used, All Nodes’ > FROM memoryusage > WHERE memory_type = ’Data memory’; 

