ndbinfo: The NDB Cluster Information Database Notes The  fq_name  contains the fully qualified name of the schema object to which this fragment replica belongs. This currently has the following formats: The  $unique  suffix shown for unique indexes is added by  mysqld ; for an index created by a different NDB API client application, this may differ, or not be present. The syntax just shown for fully qualified object names is an internal interface which is subject to change in future releases. Consider a table  t1  created and modified by the following SQL statements: •Unique index:  sys/def/ BaseTblId / IndexName $unique •Ordered index:  sys/def/ BaseTblId / IndexName •Base table:  DbName /def/ TblName • BLOB  table:  DbName /def/NDB$BLOB_ BaseTblId _ ColNo •Base table:  mydb/def/t1 • BLOB  table:  mydb/def/NDB$BLOB_11_2 •Ordered index (primary key):  sys/def/11/PRIMARY •Unique index:  sys/def/11/ix1$unique CREATE DATABASE mydb; USE mydb; CREATE TABLE t1 ( a INT NOT NULL, b INT NOT NULL, t TEXT NOT NULL, PRIMARY KEY (b) ) ENGINE=ndbcluster; CREATE UNIQUE INDEX ix1 ON t1(b) USING HASH; If  t1  is assigned table ID 11, this yields the  fq_name  values shown here: For indexes or  BLOB  tables, the  parent_fq_name  column contains the  fq_name  of the corresponding base table. For base tables, this column is always  NULL . The  type  column shows the schema object type used for this fragment, which can take any one of the values  System table ,  User table ,  Unique hash index , or  Ordered index .  BLOB  tables are shown as  User table . The  table_id  column value is unique at any given time, but can be reused if the corresponding object has been deleted. The same ID can be seen using the  ndb_show_tables  utility. The  block_instance  column shows which LDM instance this fragment replica belongs to. You can use this to obtain information about specific threads from the  threadblocks  table. The first such instance is always numbered 0. Since there are typically two fragment replicas, and assuming that this is so, each  fragment_num  value should appear twice in the table, on two different data nodes from the same node group. 4570