Manage buckets

A bucket is a named location where time series data is stored. All buckets have a retention period, a duration of time that each data point persists. InfluxDB drops all points with timestamps older than the bucket’s retention period. A bucket belongs to an organization.

If coming from InfluxDB v1, the concepts of databases and retention policies have been combined into a single concept–bucket. Retention policies are no longer part of the InfluxDB data model. However, InfluxDB Cloud Serverless does support InfluxQL and the InfluxDB v1 API /write and /query endpoints, which require databases and retention policies. See how to map v1 databases and retention policies to buckets.

If coming from InfluxDB v2 or InfluxDB Cloud, buckets are functionally equivalent.

Retention period

A bucket retention period is the maximum age of data stored in the bucket. The age of data is determined by the timestamp associated with each point. When a point’s timestamp is beyond the retention period (relative to now), the point is marked for deletion and is removed from the bucket the next time the retention enforcement service runs.

The minimum retention period for an InfluxDB bucket is 1 hour. The maximum retention period is infinite meaning data does not expire and will never be removed by the retention enforcement service.

You can update a bucket to change the retention period.

Table and column limits

In InfluxDB Cloud Serverless, table (measurement) and column are limited per bucket. Each measurement is represented by a table. Time, fields, and tags are each represented by a column.

Maximum number of tables: 500 Maximum number of columns: 200

The following articles provide information about managing buckets:

Was this page helpful?

Thank you for your feedback!

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 Serverless