Time To Become Readable

Time To Become Readable (TTBR) is the delay between when you write data to InfluxDB Cloud and when that data becomes queryable. TTBR is variable and is affected by many factors.

How write requests work in the InfluxDB Cloud API

Whenever you send a write request to the /api/v2/write endpoint, the following actions occur:

  1. API validates the request and queues the write.
  2. If the write is queued, API responds with an HTTP 204 status code.
  3. API handles the write asynchronously and reaches eventual consistency.

For more information, see /api/v2/write documentation.

The returned 204 status code does not mean that the point is queryable; it means the write request has been added to the durable write queue (for more information, see Handle write and delete responses). TTBR represents the time it takes for the write request to be queued, the write operation to be executed, and the data to become queryable.

For more information about status codes returned from the /api/v1/write endpoint

Flux vs InfluxQL

One of the primary factors that affects TTBR is the query language you use to query the newly written data. InfluxQL queries use a metadata cache that stores information about fields and series.

If you write a point with a new field, the new field will not be queryable by InfluxQL until InfluxDB Cloud refreshes the metadata cache, which can take up to 15 minutes. Flux does not rely on the metadata cache, so the newly written data should be queryable in approximately one second.

If you write a point with an existing field, and the field already exists in the metadata cache, both InfluxQL and Flux should be able to query the new data in approximately one second.

InfluxDB Cloud TTBRs

Write request toFluxInfluxQL
Existing field≈1s≈1s
New field≈1s≈10m to 15m

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 powered by TSM