AGENT-UNINSTALL

On this page

Stops a remote MemSQL Ops agent and deletes all its data.

Data will not be deleted with the --uninstall-ops-only flag.

If SingleStore nodes are already installed in the remote host, this command will prompt users to delete those nodes first before proceeding with the uninstall.

Usage

usage: memsql-ops agent-uninstall [--settings-file SETTINGS_FILE] [--async]
                                  [--agent-id AGENT_ID | --all] [--force]
                                  [--uninstall-ops-only]
                                  [--uninstall-without-prompting]
                                  [--no-prompt]

Uninstall a remote MemSQL Ops agent and all of its data.

Data will not be deleted with the --uninstall-ops-only flag.

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.
  --async               If this option is true, we will exit without waiting
                        for the MemSQL Ops agent to be fully uninstalled.
  --agent-id AGENT_ID   The ID of the agent to stop.
  --all                 Uninstall all agents in the cluster.
  --force               If this is true, we will remove this agent from the
                        system even if we cannot connect to it.
  --uninstall-ops-only  Uninstalls the MemSQL Ops agent without deleting any node data.
  --uninstall-without-prompting
                        If this is true, we will attempt to uninstall the
                        MemSQL Ops agent without prompting for confirmation.
  --no-prompt           Skip interactive prompts if ID is not provided. This
                        should be used for non-interactive scripts and
                        automation.

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.

  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