Documentation Home
NDB Cluster Internals
Download this Manual
PDF (US Ltr) - 1.1Mb
PDF (A4) - 1.1Mb
HTML Download (TGZ) - 378.4Kb
HTML Download (Zip) - 389.3Kb


2.83 DUMP 2600

Code

2600

Symbol

CmvmiDumpConnections

Kernel Block

CMVMI

Description.  Shows status of connections between all cluster nodes. When the cluster is operating normally, every connection has the same status.

Sample Output. 

Node 3: Connection to 1 (MGM) is connected
Node 3: Connection to 2 (MGM) is trying to connect
Node 3: Connection to 3 (DB) does nothing
Node 3: Connection to 4 (DB) is connected
Node 3: Connection to 7 (API) is connected
Node 3: Connection to 8 (API) is connected
Node 3: Connection to 9 (API) is trying to connect
Node 3: Connection to 10 (API) is trying to connect
Node 3: Connection to 11 (API) is trying to connect
Node 4: Connection to 1 (MGM) is connected
Node 4: Connection to 2 (MGM) is trying to connect
Node 4: Connection to 3 (DB) is connected
Node 4: Connection to 4 (DB) does nothing
Node 4: Connection to 7 (API) is connected
Node 4: Connection to 8 (API) is connected
Node 4: Connection to 9 (API) is trying to connect
Node 4: Connection to 10 (API) is trying to connect
Node 4: Connection to 11 (API) is trying to connect

Additional Information.  The message is trying to connect actually means that the node in question was not started. This can also be seen when there are unused [api] or [mysql] sections in the config.ini file nodes configured, that is, when there are spare slots for API or SQL nodes.