MEMSQL-UPDATE-CONFIG

On this page

Update or add a SingleStore database configuration as specified in the memsql.cnf configuration file.

Usage

usage: memsql-ops memsql-update-config [--settings-file SETTINGS_FILE]
                                       [--async] [--all] [--no-prompt] --key
                                       KEY [--value [VALUE]] [--delete]
                                       [--set-global]
                                       [memsql_id]

Change a config value for a SingleStore node.

positional arguments:
  memsql_id             The ID of the SingleStore node whose config you'd like to
                        update.

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 SingleStore to have its config changed.
  --all                 Update all SingleStore nodes' configs in the cluster.
  --no-prompt           Skip interactive prompts if ID is not provided. This
                        should be used for non-interactive scripts and
                        automation.
  --key KEY             The name of the config variable that you'd like to
                        change.
  --value [VALUE]       The value of the config variable that you'd like to
                        set. If you pass in this option but do not give a
                        value, we will set the config variable to an empty
                        string.
  --delete              If this value is passed in, we will delete the given
                        variable from the config instead of setting its value.
  --set-global          If this value is passed in, we will also attempt to
                        run SET GLOBAL <key>=<value> on the SingleStore node, if it
                        is running.

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