## Notes 

Status of the connection 

• remote_address 

Name or IP address of the remote host 

• bytes_sent 

Number of bytes sent using this connection 

• bytes_received 

Number of bytes received using this connection 

• connect_count 

Number of times connection established on this transporter 

• overloaded 

1 if this transporter is currently overloaded, otherwise 0 

• overload_count 

Number of times this transporter has entered overload state since connecting 

• slowdown 

1 if this transporter is in slowdown state, otherwise 0 

• slowdown_count 

Number of times this transporter has entered slowdown state since connecting 

For each running data node in the cluster, the transporters  table displays a row showing the status of each of that node’s connections with all nodes in the cluster, including itself . This information is shown in the table’s status  column, which can have any one of the following values: CONNECTING , CONNECTED , DISCONNECTING , or DISCONNECTED . 

Connections to API and management nodes which are configured but not currently connected to the cluster are shown with status DISCONNECTED . Rows where the node_id  is that of a data node which is not currently connected are not shown in this table. (This is similar omission of disconnected nodes in the ndbinfo.nodes  table. 

The remote_address  is the host name or address for the node whose ID is shown in the remote_node_id  column. The bytes_sent  from this node and bytes_received  by this node are the numbers, respectively, of bytes sent and received by the node using this connection since it was established. For nodes whose status is CONNECTING  or DISCONNECTED , these columns always display 0 . 

Assume you have a 5-node cluster consisting of 2 data nodes, 2 SQL nodes, and 1 management node, as shown in the output of the SHOW  command in the ndb_mgm  client: 

ndb_mgm> SHOW Connected to Management Server at: localhost:1186 Cluster Configuration --------------------- [ndbd(NDB)] 2 node(s) 

