SET CLUSTER

Sets a sync variable. Depending on the variable, the updated value is propagated to all nodes in the cluster or all aggregators in the cluster.

Syntax

SET CLUSTER variable_name = value

Arguments

  • variable_name: name of the sync variable.

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

Remarks

  • The last two columns in the Sync Variables Lists specify whether a variable can be synced to all aggregators, all leaves, or both. If a variable can be synced to all aggregators and all leaves, SET CLUSTER syncs the variables to all nodes. If a variable can be synced to all aggregators, only, SET CLUSTER syncs the variable to all aggregators.

  • This command must be run on the master aggregator.

  • To sync a variable to all leaves, only, run SET LEAF.

Examples

Example 1: Syncing a Variable to all Nodes

The following example sets the variable regexp_format. SET CLUSTER syncs the variable to all nodes, because this specific variable can be synced to all aggregators and all leaves, as indicated in the last sentence of the Description column for the variable.

SET CLUSTER regexp_format = "extended";

Retrieve the variable’s value:

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

Example 2: Syncing a Variable to All Aggregators

The following example sets the variable default_autostats_enabled. SET CLUSTER syncs the variable to all aggregators, because this specific variable can be synced to all aggregators, only, as indicated in the last sentence of the Description column for the variable.

SET CLUSTER default_autostats_enabled = true;

Retrieve the variable’s value:

SELECT @@default_autostats_enabled;
+-----------------------------+
| @@default_autostats_enabled |
+-----------------------------+
|                           1 |
+-----------------------------+

Last modified: June 22, 2022

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