Sign inTry Free

Important

Self-managed SingleStore will soon transition from version 9.1 RC to version 10. This new semantic versioning scheme will provide SingleStore with finer control over engine and feature releases that were not possible with the current versioning scheme.

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 prior to its general availability. Ahead of this transition, SingleStore 9.0 is recommended for production workloads, which can later be upgraded to SingleStore 10.

SET LEAF

On this page

The SET LEAF command sets a sync variable to propagate to all leaves in the cluster.

Syntax

SET LEAF variable_name = value

Arguments

  • variable_name: name of the sync variable.

  • value: value to be assigned to the sync variable.

Remarks

  • variable_name must be a sync variable that can sync to all nodes (aggregators and leaves).

  • You cannot this command on a non-sync variable.

  • This command must be run on the master aggregator.

Examples

Example 1

The following example syncs the variable regexp_format to all leaves. SET LEAF can be run on regexp_format because regexp_format is a variable that can sync to all nodes (leaves and aggregators).

This is indicated in the last sentence of the Description column for the variable.

SET LEAF regexp_format = "extended";

Retrieve the variable’s value:

SELECT @@regexp_format;
+-----------------+
| @@regexp_format |
+-----------------+
| extended        |
+-----------------+

Example 2

The following example attempts to sync the variable auto_attach to all leaves. SET LEAF fails because auto_attach is a variable that can sync to all aggregators, only.

This is indicated in the last sentence of the Description column for the variable.

SET LEAF auto_attach = 1;
ERROR 2324 (HY000): This cluster-wide variable exists only on
aggregators, it's not possible to set a value for leaves

Related Topics

Last modified:

Was this article helpful?

On this page

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