Instance List
The instance list screen gathers the nodes in a SingleStore cluster into a table, one per row. Because you can check the aggregator and leaf nodes together on one screen, it serves as the starting point for quickly scanning the overall cluster state and drilling straight into a problematic node.
Summary area
The area above the table shows the total node count and a breakdown by state.
| Item | Description |
|---|---|
| Total | Total number of nodes being collected |
| Critical | Number of nodes classified as critical |
| Warning | Number of nodes classified as warning |
| Normal | Number of nodes in a normal state |
Node list table
Each row corresponds to one node. The default columns are as follows.
| Item | Description |
|---|---|
| Status | The collection and state of the node |
| Server Name | Node name (for example, 1-MA-150, LF-152). Click it to go to the corresponding Instance Monitoring |
| IP | Node IP address |
| Port | Connection port (default 3306) |
| Database | List of databases the node is responsible for |
| ROLE | Node role. MA (Master Aggregator), CA (Child Aggregator), Leaf |
Cluster Name | Name of the cluster the node belongs to |
Threads_running | Number of running threads |
Questions | Number of processed queries |
innodb_buffer_pool_read_requests | Number of buffer pool read requests |
lock_wait_sessions | Number of sessions waiting on a lock |
Note
For SingleStore, when you install the DBX agent only on an aggregator node, it auto-detects leaf nodes through MV_NODES and the entire cluster appears in the list. You can quickly distinguish roles by the MA, CA, and LF prefixes in node names.
Working with the table
- Column selection: You can add or hide the columns shown in the table.
- Multi-view: Select multiple nodes to switch to a screen that compares them together.
- After selecting a node, you can drill into the detail screen to examine its metrics and sessions in detail.
Data interpretation guide
| Checkpoint | Description |
|---|---|
Sudden spike in Threads_running on a specific node | Suspect load or contention concentrated on that node |
Accumulating lock_wait_sessions | Lock waits are occurring; trace the cause with Lock Tree |
| Metric deviation among Leaf nodes | Possible data skew; check the layout in Partition |