Data retention in InfluxDB Cloud Serverless

InfluxDB Cloud Serverless enforces bucket retention periods at query time. Any points with timestamps beyond a bucket’s retention period are filtered out of query results, even though the data may still exist.

Bucket retention period

A bucket retention period is the duration of time that a bucket retains data. Retention periods are designed to automatically delete expired data and optimize storage without any user intervention.

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 not queryable, but may still exist in storage until fully deleted.

View bucket retention periods

Use the influx bucket list command to view your buckets’ retention periods.

When does data actually get deleted?

InfluxDB routinely deletes Parquet files containing only expired data. InfluxDB retains expired Parquet files for at least 100 days for disaster recovery. After the disaster recovery period, expired Parquet files are permanently deleted and can’t be recovered.

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:

State of the InfluxDB Cloud Serverless documentation

InfluxDB Cloud Serverless documentation is a work in progress.

The new documentation for InfluxDB Cloud Serverless is a work in progress. We are adding new information and content almost daily. Thank you for your patience!

If there is specific information you’re looking for, please submit a documentation issue.

InfluxDB Cloud Serverless