MV_NODES

This view describes all SingleStore Helios nodes in the workspace.

The view holds one row per node.

mv_nodes may only be queried while connected to an aggregator node.

Column name	Description
`id`	The ID of the node. This ID matches the `node_id` reported for tasks running on the node.
`ip_addr`	The IP address of the node.
`port`	The port on which the node is listening.
`type`	The type of a given node: `MA`, `Leaf`, or `CA`.
`state`	The state of a given node: `Online`, `Offline`, `Detached`, or `Attaching`.
`availability_group`	The `ID` of the related availability group for a given node.
`num_cpus`	The number of CPUs available to a given node.
`max_memory_mb`	The maximum memory use, in MB, of a given node. This is the same value as the engine variable `maximum_memory`.
`max_table_memory_mb`	The maximum memory, in MB, that can be used for table storage. This is the value value as the engine variable `maximum_table_memory`.
`memory_used_mb`	The amount of memory, in MB, used on a given node for storing tables, query execution, and any other purposes.
`table_memory_used_mb`	The amount of memory, in MB, used on a given node to store table data.
`total_data_disk_mb`	The total amount of disk storage, in MB.
`available_data_disk_mb`	The amount of available disk storage, in MB.
`uptime`	The amount of time in seconds that a node has been running.
`version`	The version of SingleStore that a given node is running on.

Last modified: August 29, 2022

Was this article helpful?

Verification instructions

Note: You must install cosign to verify the authenticity of the SingleStore file.

Use the following steps to verify the authenticity of singlestoredb-server, singlestoredb-toolbox, singlestoredb-studio, and singlestore-client SingleStore files that have been downloaded.

You may perform the following steps on any computer that can run cosign, such as the main deployment host of the cluster.

(Optional) Run the following command to view the associated signature files.
Shell
```
curl undefined
```
Download the signature file from the SingleStore release server.
- Option 1: Click the Download Signature button next to the SingleStore file.
- Option 2: Copy and paste the following URL into the address bar of your browser and save the signature file.
- Option 3: Run the following command to download the signature file.
  Shell
```
curl -O undefined
```

After the signature file has been downloaded, run the following command to verify the authenticity of the SingleStore file.

Shell

echo -n undefined |
    cosign verify-blob --certificate-oidc-issuer https://oidc.eks.us-east-1.amazonaws.com/id/CCDCDBA1379A5596AB5B2E46DCA385BC \
      --certificate-identity https://kubernetes.io/namespaces/freya-production/serviceaccounts/job-worker \
      --bundle undefined \
      --new-bundle-format -

Verified OK