content_image/718507.jpg content_image/718516.jpg content_image/718517.jpg
The start_phase  column uses the same range of values as those used in the output of the ndb_mgm client node_id  STATUS  command (see Section 23.5.1, “Commands in the NDB Cluster Management Client” ). If the node is not currently starting, then this column shows 0 . For a listing of NDB Cluster start phases with descriptions, see Section 23.5.4, “Summary of NDB Cluster Start Phases” . 

The config_generation  column shows which version of the cluster configuration is in effect on each data node. This can be useful when performing a rolling restart of the cluster in order to make changes in configuration parameters. For example, from the output of the following SELECT  statement, you can see that node 3 is not yet using the latest version of the cluster configuration ( 6 ) although nodes 1, 2, and 4 are doing so: 

mysql> USE ndbinfo; Database changed mysql> SELECT * FROM nodes; 

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

2 rows in set (0.04 sec) 

Therefore, for the case just shown, you should restart node 3 to complete the rolling restart of the cluster. 

Nodes that are stopped are not accounted for in this table. Suppose that you have an NDB Cluster with 4 data nodes (node IDs 1, 2, 3 and 4), and all nodes are running normally, then this table contains 4 rows, 1 for each data node: 

mysql> USE ndbinfo; Database changed mysql> SELECT * FROM nodes; 

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

4 rows in set (0.04 sec) 

If you shut down one of the nodes, only the nodes that are still running are represented in the output of this SELECT  statement, as shown here: 

## 23.5.14.39 The ndbinfo operations_per_fragment Table 

ndb_mgm> 2 STOP Node 2: Node shutdown initiated Node 2: Node shutdown completed. Node 2 has shutdown. 

mysql> SELECT * FROM nodes; 

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

3 rows in set (0.02 sec) 

