content_image/786747.jpg content_image/786753.jpg
Number of attributes: 4 Number of primary keys: 1 Length of frm data: 1001 Max Rows: 0 Row Checksum: 1 Row GCI: 1 SingleUserMode: 0 ForceVarPart: 1 PartitionCount: 2 FragmentCount: 2 PartitionBalance: FOR_RP_BY_LDM ExtraRowGciBits: 0 ExtraRowAuthorBits: 0 TableStatus: Retrieved Table options: readbackup HashMap: DEFAULT-HASHMAP-3840-2 Tablespace id: 16 Tablespace: ts_1 -- Attributes -- id Int PRIMARY KEY DISTRIBUTION KEY AT=FIXED ST=MEMORY AUTO_INCR name Varchar(80;utf8mb4_0900_ai_ci) NOT NULL AT=SHORT_VAR ST=MEMORY length_mm Int NOT NULL AT=FIXED ST=DISK weight_gm Int NOT NULL AT=FIXED ST=DISK -- Indexes -- PRIMARY KEY(id) - UniqueHashIndex PRIMARY(id) - OrderedIndex uk(name) - OrderedIndex uk$unique(name) - UniqueHashIndex -- Per partition info -- 

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

This means that 1048576 bytes are allocated from the tablespace for this table on each partition, of which 1044440 bytes remain free for additional storage. In other words, 1048576 - 1044440 = 4136 bytes per partition is currently being used to store the data from this table’s disk-based columns. The number of bytes shown as Free extent_space  is available for storing on-disk column data from the fish  table only; for this reason, it is not visible when selecting from the INFORMATION_SCHEMA.FILES  table. 

Tablespace id  and Tablespace  are displayed for Disk Data tables beginning with NDB 8.0.21. 

For fully replicated tables, ndb_desc  shows only the nodes holding primary partition fragment replicas; nodes with copy fragment replicas (only) are ignored. You can obtain such information, using the mysql  client, from the table_distribution_status , table_fragments , table_info , and table_replicas  tables in the ndbinfo  database. 

All options that can be used with ndb_desc  are shown in the following table. Additional descriptions follow the table. 

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

