Documentation

Data retention in InfluxDB Cloud

The InfluxDB Cloud retention enforcement service checks for and removes data with timestamps beyond the defined retention period of the bucket the data is stored in. This service is designed to automatically delete “expired” data and optimize disk usage without any user intervention.

Bucket retention period

A bucket retention period is the duration of time that a bucket retains data. Retention periods can be as short as an hour or infinite. Points in a bucket with timestamps beyond the defined retention period (relative to now) are flagged for deletion (also known as “tombstoned”).

View bucket retention periods

Use the influx bucket list command to view the retention period buckets in your organization.

When does data actually get deleted?

The InfluxDB Cloud retention enforcement service runs hourly and tombstones all points with timestamps beyond the bucket retention period. Tombstoned points persist on disk, but are filtered from all query results until the next compaction cycle, when they are removed from disk. Compaction cycle intervals vary.


Was this page helpful?

Thank you for your feedback!


Introducing InfluxDB Clustered

A highly available InfluxDB 3.0 cluster on your own infrastructure.

InfluxDB Clustered is a highly available InfluxDB 3.0 cluster built for high write and query workloads on your own infrastructure.

InfluxDB Clustered is currently in limited availability and is only available to a limited group of InfluxData customers. If interested in being part of the limited access group, please contact the InfluxData Sales team.

Learn more
Contact InfluxData Sales

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.

Flux is going into maintenance mode and will not be supported in InfluxDB 3.0. This was a decision based on the broad demand for SQL and the continued growth and adoption of InfluxQL. We are continuing to support Flux for users in 1.x and 2.x so you can continue using it with no changes to your code. If you are interested in transitioning to InfluxDB 3.0 and want to future-proof your code, we suggest using InfluxQL.

For information about the future of Flux, see the following:

InfluxDB Cloud powered by TSM