Transactions: NO XA: NO Savepoints: NO *************************** 10. row *************************** Engine: MEMORY Support: YES Comment: Hash based, stored in memory, useful for temporary tables Transactions: NO XA: NO Savepoints: NO 10 rows in set (0.00 sec) 

If ndbinfo  support is enabled, then you can access ndbinfo  using SQL statements in mysql  or another MySQL client. For example, you can see ndbinfo  listed in the output of SHOW DATABASES , as shown here (emphasized text): 

mysql> SHOW DATABASES; +--------------------+ | Database | +--------------------+ | information_schema | | mysql | | ndbinfo | | performance_schema | | sys | +--------------------+ 5 rows in set (0.04 sec) 

If the mysqld  process was not started with the --ndbcluster  option, ndbinfo  is not available and is not displayed by SHOW DATABASES . If mysqld  was formerly connected to an NDB Cluster but the cluster becomes unavailable (due to events such as cluster shutdown, loss of network connectivity, and so forth), ndbinfo  and its tables remain visible, but an attempt to access any tables (other than blocks  or config_params ) fails with Got error 157 ’Connection to NDB failed’ from NDBINFO . 

With the exception of the blocks  and config_params  tables, what we refer to as ndbinfo  “tables”  are actually views generated from internal NDB  tables not normally visible to the MySQL Server. 

All ndbinfo  tables are read-only, and are generated on demand when queried. Because many of them are generated in parallel by the data nodes while other are specific to a given SQL node, they are not guaranteed to provide a consistent snapshot. 

In addition, pushing down of joins is not supported on ndbinfo  tables; so joining large ndbinfo  tables can require transfer of a large amount of data to the requesting API node, even when the query makes use of a WHERE  clause. 

ndbinfo  tables are not included in the query cache. (Bug #59831) 

You can select the ndbinfo  database with a USE  statement, and then issue a SHOW TABLES  statement to obtain a list of tables, just as for any other database, like this: 

mysql> USE ndbinfo; Database changed mysql> SHOW TABLES; +---------------------------------+ | Tables_in_ndbinfo | +---------------------------------+ | arbitrator_validity_detail | | arbitrator_validity_summary | | blocks | | cluster_locks | | cluster_operations | 

