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.

Global Variables

Warning

You can set a sync variable on the Master Aggregator only. You will receive an error if you attempt to set a sync variable on any other type of SingleStore node.

You should not set a sync variable by editing the memsql.cnf file. Attempting to do so may result in an error, or the setting may have no effect. Instead, set sync variables using methods described here.

For advanced users, a globalVariables section can also be declared. This is an optional section that allows values to be specified for SingleStore engine variables.

YAML

...
globalVariables:
  snapshots_to_keep: "6"
  transaction_buffer: "8m"
  default_partitions_per_leaf: "4"

Refer to Engine Variables and List of Engine Variables documentation for more information about engine variables, global variables, and when to use them.

As of Operator 1.2.1, nearly all engine variables are supported except for:

bottomless_storage_location
cloud_permissions
cluster_name
enable_bottomless
enable_sites
expected_leaf_core_count
redundancy_level
sync_permissions

Note that some engine variables can be set prior to deploying a new cluster, but cannot be set once the cluster is running.

SYNC variables may be set at launch of a new cluster. Once the cluster is online and running, these variables must then be set through a database connection.
NON-SYNC variables may be set in the globalVariables section of the MemsqlCluster spec.

Refer to the List of Engine Variables for more information.

Note

If it is not overridden in the globalVariables section, the Operator will set default_partitions_per_leaf to a value equal to the height multiplied by the vCPU cores per unit.

Both aggregatorSpec and leafSpec-specific globalVariables sections may be declared. The optional spec.aggregatorSpec and spec.leafSpec sections in the sdb-cluster.yaml file allow non-sync variables for aggregators and leaf nodes to be specified separately.

YAML

aggregatorSpec:
  ...
  globalVariables:
    snapshots_to_keep: "4"

...
leafSpec:
  ...
  globalVariables:
    snapshots_to_keep: "5"

Once the sync and non-sync variables are set via spec.globalVarialbes, they are applied across the entire cluster.

All variables set via spec.aggregatorSpec.globalVariables are applied to all pods in Master Aggregator and child aggregators.
All variables set via spec.leafSpec.globalVariables are applied to all pods in leaf nodes.

Include only non-sync variables in spec.aggregatorSpec.globalVariables and spec.leafSpec.globalVariables.

Non-sync variables defined in spec.aggregatorSpec.globalVariables and spec.leafSpec.globalVariables override the same variables defined in spec.globalVariables.

Global Variables

Was this article helpful?

Was this article helpful?