content_image/736849.jpg content_image/736850.jpg
USE LOGFILE GROUP mygroup INITIAL_SIZE 256M ENGINE NDBCLUSTER; 

After running these two statements successfully, you should see a result similar to the one shown here for this query against the FILES  table: 

mysql> SELECT LOGFILE_GROUP_NAME, FILE_TYPE, EXTRA -> FROM INFORMATION_SCHEMA.FILES -> WHERE ENGINE = ’ndbcluster’; 

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

The undo log buffer size information was inadvertently removed in NDB 8.0.13, but was restored in NDB 8.0.15. (Bug #92796, Bug #28800252) 

Prior to NDB 8.0.13, the FILES  table contained a row for each of these files on each data node the file belonged to, as well as the size of its undo buffer. In these versions, the result of the same query contains one row per data node, as shown here: 

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

## Notes 

## InnoDB Notes 

• FILES  is a nonstandard INFORMATION_SCHEMA  table. 

•As of MySQL 8.0.21, you must have the PROCESS  privilege to query this table. 

The following notes apply to InnoDB  data files. 

•Data reported by FILES  is reported from the InnoDB  in-memory cache for open files. By comparison, INNODB_DATAFILES  reports data from the InnoDB SYS_DATAFILES  internal data dictionary table. 

•The data reported by FILES  includes global temporary tablespace data. This data is not available in the InnoDB SYS_DATAFILES  internal data dictionary table, and is therefore not reported by INNODB_DATAFILES . 

•Undo tablespace data is reported by FILES  when separate undo tablespaces are present, which they are by default in MySQL 8.0 

•The following query returns all data pertinent to InnoDB  tablespaces. 

SELECT FILE_ID, FILE_NAME, FILE_TYPE, TABLESPACE_NAME, FREE_EXTENTS, TOTAL_EXTENTS, EXTENT_SIZE, INITIAL_SIZE, MAXIMUM_SIZE, 

