Documentation

Flux query management

Configuration settings for Flux query management

The following configuration settings are in the flux-controller section of the configuration file.

[flux-controller]

query-concurrency

Number of queries allowed to execute concurrently. 0 means unlimited. Default is 0.

query-initial-memory-bytes

Initial bytes of memory allocated for a query. 0 means unlimited. Default is 0.

query-max-memory-bytes

Maximum total bytes of memory allowed for an individual query. 0 means unlimited. Default is 0.

total-max-memory-bytes

Maximum total bytes of memory allowed for all running Flux queries. 0 means unlimited. Default is 0.

query-queue-size

Maximum number of queries allowed in execution queue. When queue limit is reached, new queries are rejected. 0 means unlimited. Default is 0.


Was this page helpful?

Thank you for your feedback!


Telegraf Enterprise now in public beta

Get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

See the Blog Post

The upcoming Telegraf Enterprise offering is for organizations running Telegraf at scale and is comprised of two key components:

  • Telegraf Controller: A control plane (UI + API) that centralizes Telegraf configuration management and agent health visibility.
  • Telegraf Enterprise Support: Official support for Telegraf Controller and Telegraf plugins.

Join the Telegraf Enterprise beta to get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

For more information:

New in InfluxDB 3.8

Key enhancements in InfluxDB 3.8 and the InfluxDB 3 Explorer 1.6.

See the Blog Post

InfluxDB 3.8 is now available for both Core and Enterprise, alongside the 1.6 release of the InfluxDB 3 Explorer UI. This release is focused on operational maturity and making InfluxDB easier to deploy, manage, and run reliably in production.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On May 27, 2026, the latest tag for InfluxDB Docker images will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments.

If using Docker to install and run InfluxDB, the latest tag will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments. For example, if using Docker to run InfluxDB v2, replace the latest version tag with a specific version tag in your Docker pull command–for example:

docker pull influxdb:2