Sign inTry Free

Important

The SingleStore 9.1 release candidate (RC) is available now. It will be promoted to general availability (GA) soon and at that time it will be renamed to SingleStore 10.

In the interim, SingleStore 9.1 RC can be used to preview, evaluate, and provide feedback on the new and upcoming features in SingleStore 10, while SingleStore 9.0 is recommended for production workloads.

MV_SYSINFO_DISK

This view describes the total disk usage breakdown of SingleStore and other processes.

Column name

Description

node_id

The ID of the node.

ip_addr

The IP address of the node.

port

The port on which the node is listening.

type

MA, Leaf, or CA

mount_name

The name of the mount_point for directories in memsql_dirs.

mount_point

The location of the mount.

memsql_dirs

The comma separated list of SingleStore directories (data, plancache, tracelogs) that are tracked.

mount_total_b

The total size of the disk, in bytes, for mount_point.

mount_used_b

The total bytes used by the disk at mount_point.

read_cumulative_b

The total bytes read from the disk across all mount points since the starting of the process.

write_cumulative_b

The total bytes written to the disk across all mount points since the starting of the process.

timestamp_ns

The time when the data was received.

read_operations_cumulative_per_device

Number of read operations performed by the device since start up.

write_operations_cumulative_per_device

Number of write operations performed by the device since start up.

device_name

Name of the device to which the values in read_operations_cumulative_per_device and write_operations_cumulative_per_device are associated.

Last modified:

Was this article helpful?

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.

  1. (Optional) Run the following command to view the associated signature files.

    curl undefined

  2. 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.

      curl -O undefined

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

    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

Try Out This Notebook to See What’s Possible in SingleStore

Get access to other groundbreaking datasets and engage with our community for expert advice.

Sign UpLog In