Documentation

Manage environment variables in your InfluxDB Cluster

Use environment variables to define settings for individual components in your InfluxDB cluster and adjust your cluster’s running configuration. Define environment variables for each component in your AppInstance resource.

InfluxDB Clustered components support various environment variables. While many of these variables have default settings, you can customize them by setting your own values.

Overriding default settings may affect overall cluster performance

InfluxDB Clustered components have complex interactions that can be affected when overriding default configuration settings. Changing these settings may impact overall cluster performance. Before making configuration changes using environment variables, consider consulting InfluxData Support to identify any potential unintended consequences.

AppInstance component schema

In your AppInstance resource, configure individual component settings in the spec.package.spec.components property if configuring your AppInstance resource directly or, if using Helm, use the components property in your values.yaml. This property supports the following InfluxDB Clustered component keys:

  • ingester
  • querier
  • router
  • compactor
  • garbage-collector
apiVersion: kubecfg.dev/v1alpha1
kind: AppInstance
metadata:
  name: influxdb
  namespace: influxdb
spec:
  package:
    # ...
    spec:
      components:
        ingester:
          # Ingester settings ...
        querier:
          # Querier settings ...
        router:
          # Router settings. ...
        compactor:
          # Compactor settings ...
        garbage-collector:
          # Garbage collector settings ...
# ...
components:
  ingester:
    # Ingester settings ...
  querier:
    # Querier settings ...
  router:
    # Router settings. ...
  compactor:
    # Compactor settings ...
  garbage-collector:
    # Garbage collector settings ...

For more information about components in the InfluxDB v3 storage engine, see the InfluxDB v3 storage engine architecture.

Set environment variables for a component

  1. Under the specific component property, use the <component>.template.containers.iox.env property to define environment variables.

  2. In the env property, structure each environment variable as a key-value pair where the key is the environment variable name and the value is the environment variable value (string-formatted). For example, to configure environment variables for the Garbage collector:

    apiVersion: kubecfg.dev/v1alpha1
    kind: AppInstance
    metadata:
      name: influxdb
      namespace: influxdb
    spec:
      package:
        # ...
        spec:
          components:
            garbage-collector:
              template:
                containers:
                  iox:
                    env:
                      INFLUXDB_IOX_GC_OBJECTSTORE_CUTOFF: '6h'
                      INFLUXDB_IOX_GC_PARQUETFILE_CUTOFF: '6h'
    
    # ...
    components:
      garbage-collector:
        template:
          containers:
            iox:
              env:
                INFLUXDB_IOX_GC_OBJECTSTORE_CUTOFF: '6h'
                INFLUXDB_IOX_GC_PARQUETFILE_CUTOFF: '6h'
    
  3. Apply the configuration changes to your cluster and add or update environment variables in each component.

    kubectl apply \
      --filename myinfluxdb.yml \
      --namespace influxdb
    
    helm upgrade \
      influxdata/influxdb3-clustered \
      -f ./values.yml \
      --namespace influxdb
    

Update environment variables instead of removing them

Most configuration settings that can be overridden by environment variables have default values that are used if the environment variable is unset. Removing environment variables from your AppInstance resource configuration will not remove those environment variables entirely; instead, they will revert to their default settings. To revert to the default settings, simply unset the environment variable or update the value in your AppInstance resource to the default value.

In the preceding example, the INFLUXDB_IOX_GC_OBJECTSTORE_CUTOFF environment variable is set to 6h. If you remove INFLUXDB_IOX_GC_OBJECTSTORE_CUTOFF from the env property, the cutoff reverts to its default setting of 30d.

View example of environment variables in all components


Was this page helpful?

Thank you for your feedback!


The future of Flux

Flux is going into maintenance mode. You can continue using it as you currently are without any changes to your code.

Read more

InfluxDB v3 enhancements and InfluxDB Clustered is now generally available

New capabilities, including faster query performance and management tooling advance the InfluxDB v3 product line. InfluxDB Clustered is now generally available.

InfluxDB v3 performance and features

The InfluxDB v3 product line has seen significant enhancements in query performance and has made new management tooling available. These enhancements include an operational dashboard to monitor the health of your InfluxDB cluster, single sign-on (SSO) support in InfluxDB Cloud Dedicated, and new management APIs for tokens and databases.

Learn about the new v3 enhancements


InfluxDB Clustered general availability

InfluxDB Clustered is now generally available and gives you the power of InfluxDB v3 in your self-managed stack.

Talk to us about InfluxDB Clustered