Watch the 7.3 Webinar On-Demand
This new release brings updates to Universal Storage, query optimization, and usability that you won’t want to miss.

Global Variables

For advanced users, you may also declare a globalVariables section. This is an optional section that allows you to specify values for SingleStore DB engine variables.

  • Prior to Operator 1.2.0, the supported engine variables are:

    • default_partitions_per_leaf
    • columnstore_segment_rows
    • columnstore_flush_bytes
    • columnstore_window_size
    • transaction_buffer
    • snapshot_trigger_size
    • minimal_disk_space
    • pipelines_max_concurrent
    • auditlog_level
  • As of Operator 1.2.0, nearly all engine variables are supported except for:

    • redundancy_level
    • sync_permissions
    • local_file_system_access_restricted
  • As of Operator 1.2.1, nearly all engine variables are supported except for:

    • redundancy_level
    • sync_permissions
  • Refer to List of Engine Variables for more information.

    globalVariables:
      transaction_buffer: "8m"
      default_partitions_per_leaf: "4"
    
Info

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 also be declared. These are optional sections that allow non-sync variables for aggregators and leaf nodes to be specified separately.

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

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