Documentation

Delete a Distinct Value Cache

Use the influxdb3 delete distinct_cache command to delete a Distinct Value Cache (DVC). Provide the following:

  • Database (-d, --database): (Required) The name of the database that the DVC you want to delete is associated with. You can also use the INFLUXDB3_DATABASE_NAME environment variable to specify the database.
  • Token (--token): (Required) Your InfluxDB 3 Core

authentication token. You can also use the INFLUXDB3_AUTH_TOKEN environment variable to specify the token.

  • Table (-t, --table): (Required) The name of the table that the DVC you want to delete is associated with.
  • Cache name: The name of the DVC to delete.
influxdb3 delete distinct_cache \
  --database 
DATABASE_NAME
\
--token
AUTH_TOKEN
\
--table
TABLE_NAME
\
DVC_NAME

Replace the following:

  • DATABASE_NAME: the name of the database that the DVC you want to delete is associated with
  • AUTH_TOKEN: your InfluxDB 3 Core admin authentication token
  • TABLE_NAME: the name of the table associated with the DVC you want to delete
  • DVC_NAME: the name of the DVC to delete

This is a destructive action that cannot be undone. Once deleted, any queries against the deleted DVC will return an error.


Was this page helpful?

Thank you for your feedback!


InfluxDB 3.9: Performance upgrade preview

InfluxDB 3 Enterprise 3.9 includes a beta of major performance upgrades with faster single-series queries, wide-and-sparse table support, and more.

InfluxDB 3 Enterprise 3.9 includes a beta of major performance and feature updates.

Key improvements:

  • Faster single-series queries
  • Consistent resource usage
  • Wide-and-sparse table support
  • Automatic distinct value caches for reduced latency with metadata queries

Preview features are subject to breaking changes.

For more information, see:

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:

Telegraf Controller v0.0.6-beta now available

Telegraf Controller v0.0.6-beta is now available with new features, improvements, and bug fixes.

View the release notes
Download Telegraf Controller v0.0.6-beta

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