Customize your cluster scale
InfluxDB Clustered lets you scale each component in your cluster individually, so you can customize your cluster’s scale to address the specific the specific needs of your workload. For example, if you have a heavy write workload, but not a heavy query workload, you can scale your Router and Ingester both vertically and horizontally to increase your write throughput and latency.
Default scale settings
- 1 router: Additional routers increase your cluster’s ability to handle concurrent write requests.
- 3 ingesters: Ensures redundancy on the write path.
- 1 querier: The optimal number of queriers depends on the number of concurrent queries you are likely to have and how long they take to execute.
- 1 compactor: While you can have multiple compactors, it is more efficient to scale the compactor vertically (assign more CPU and memory) rather than horizontally (increase the number of compactors).
- 1 garbage collector: The garbage collector is a light-weight process that only needs to be scaled vertically when you observe high resource usage by the garbage collector. The garbage collector cannot be scaled horizontally.
The default values provide a good starting point for testing. Once you have your cluster up and running and are looking for scaling recommendations for your anticipated workload, please contact the InfluxData Support team. We are happy to work with you to identify appropriate scale settings based on your anticipated workload.
Customize scale settings
Your AppInstance resource controls the scale of components in your InfluxDB
cluster. You can edit AppInstance resource directly or, if using the
InfluxDB Clustered Helm chart
to manage your deployment, you can edit resource settings in your values.yaml.
For specific scaling recommendations and guidelines, see Scale your cluster.
With Kubernetes, you can define both the minimum resources to request for each component and resource limits to apply to each component.
To use custom scale settings for your InfluxDB cluster, edit values for the
following fields in your myinfluxdb.yml.
If omitted, your cluster uses the default scale settings.
spec.package.spec.resourcesingesterrequestscpu: Minimum CPU resource units to assign to ingestersmemory: Minimum memory resource units to assign to ingestersreplicas: Number of ingester replicas to provision
limitscpu: Maximum CPU resource units to assign to ingestersmemory: Maximum memory resource units to assign to ingesters
compactorrequestscpu: Minimum CPU resource units to assign to compactorsmemory: Minimum memory resource units to assign to compactorsreplicas: Number of compactor replicas to provision
limitscpu: Maximum CPU resource units to assign to compactorsmemory: Maximum memory resource units to assign to compactors
querierrequestscpu: Minimum CPU resource units to assign to queriersmemory: Minimum memory resource units to assign to queriersreplicas: Number of querier replicas to provision
limitscpu: Maximum CPU resource units to assign to queriersmemory: Maximum memory resource units to assign to queriers
routerrequestscpu: Minimum CPU resource units to assign to routersmemory: Minimum memory resource units to assign to routersreplicas: Number of router replicas to provision
limitscpu: Maximum CPU Resource units to assign to routersmemory: Maximum memory resource units to assign to routers
garbage-collectorrequestscpu: Minimum CPU resource units to assign to the garbage collectormemory: Minimum memory resource units to assign to the garbage collector
limitscpu: Maximum CPU Resource units to assign to the garbage collectormemory: Maximum memory resource units to assign to the garbage collector
To use custom scale settings for your InfluxDB cluster, modify the following fields
in your values.yaml. If omitted, your cluster will use the default scale settings.
resourcesingesterrequestscpu: Minimum CPU resource units to assign to ingestersmemory: Minimum memory resource units to assign to ingestersreplicas: Number of ingester replicas to provision
limitscpu: Maximum CPU resource units to assign to ingestersmemory: Maximum memory resource units to assign to ingesters
compactorrequestscpu: Minimum CPU resource units to assign to compactorsmemory: Minimum memory resource units to assign to compactorsreplicas: Number of compactor replicas to provision
limitscpu: Maximum CPU resource units to assign to compactorsmemory: Maximum memory resource units to assign to compactors
querierrequestscpu: Minimum CPU resource units to assign to queriersmemory: Minimum memory resource units to assign to queriersreplicas: Number of querier replicas to provision
limitscpu: Maximum CPU resource units to assign to queriersmemory: Maximum memory resource units to assign to queriers
routerrequestscpu: Minimum CPU resource units to assign to routersmemory: Minimum memory resource units to assign to routersreplicas: Number of router replicas to provision
limitscpu: Maximum CPU Resource units to assign to routersmemory: Maximum memory resource units to assign to routers
garbage-collectorrequestscpu: Minimum CPU resource units to assign to the garbage collectormemory: Minimum memory resource units to assign to the garbage collector
limitscpu: Maximum CPU Resource units to assign to the garbage collectormemory: Maximum memory resource units to assign to the garbage collector
Related Kubernetes documentation
Apply the changes to your cluster
Use kubectl or helm (if using the InfluxDB Clustered Helm chart), to apply
the changes to your cluster:
kubectl apply \
--filename myinfluxdb.yml \
--namespace influxdb
helm upgrade \
influxdata/influxdb3-clustered \
-f ./values.yml \
--namespace influxdb
Was this page helpful?
Thank you for your feedback!
Support and feedback
Thank you for being part of our community! We welcome and encourage your feedback and bug reports for InfluxDB and this documentation. To find support, use the following resources:
Customers with an annual or support contract can contact InfluxData Support.