MEMSQL-LIST

On this page

List information about all MemSQL Ops nodes in the cluster. This command can be used to filter MemSQL Ops nodes based on SingleStore database roles.

This command can be used in conjunction with other memsql-ops commands to achieve more robust functionality. Here is a simple example:

memsql-ops memsql-list --agent-id Ad916a -q | xargs -n 1 memsql-ops memsql-restart --no-prompt

This command will restart all SingleStore nodes running in a particular agent with ID prefixed by Ad916a.

Usage

usage: memsql-ops memsql-list [--settings-file SETTINGS_FILE] [-q] [-j]
                              [-r {leaf,aggregator,master} [{leaf,aggregator,master} ...]
                              | --availability-group {1,2}]
                              [--agent-id AGENT_ID | --local]
                              [--include-unmonitored]

List SingleStore nodes in the cluster.

optional arguments:
  --settings-file SETTINGS_FILE
                        A path to a MemSQL Ops settings.conf file. If not set,
                        we will use the file in the same directory as the
                        MemSQL Ops binary.
  -q, --quiet           Only display SingleStore ids.
  -j, --json            Print output as JSON.
  -r {leaf,aggregator,master} [{leaf,aggregator,master} ...], --memsql-role {leaf,aggregator,master} [{leaf,aggregator,master} ...]
                        Only list SingleStore nodes with the specified role.
  --availability-group {1,2}
                        Only show leaves in the specified availability group.
  --agent-id AGENT_ID   Only list SingleStore nodes that are collocated with the
                        specified agent.
  --local               Only list SingleStore nodes which are on the local MemSQL
                        Ops agent.
  --include-unmonitored
                        Include nodes that we have unmonitored.

Last modified: April 25, 2023

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