InfluxDB Cloud Serverless limits and adjustable quotas

InfluxDB Cloud Serverless applies (non-adjustable) global system limits and adjustable service quotas on a per organization basis.

Review adjustable service quotas and global limits to plan for your bandwidth needs:

• Adjustable service quotas
  • Storage-level
    • Terminology
    • Storage-level limits
  • Free Plan
  • Usage-Based Plan
• Global limits
• Error messages when exceeding quotas or limits
  • Storage level Errors
    • Maximum number of columns reached
      • Potential solutions
    • Maximum number of tables reached
  • Error messages in the UI
  • API error response messages

Adjustable service quotas

To reduce the chance of unexpected charges and protect the service for all users, InfluxDB Cloud Serverless has adjustable service quotas applied per account.

Storage-level

The InfluxDB v3 storage engine enforces limits on the storage level that apply to all accounts (Free Plan and Usage-Based Plan).

• Terminology
• Service-level limits

Terminology

• namespace: organization+bucket
• table: measurement
• column: time, tags and fields are structured as columns

Storage-level limits

The v3 storage engine enforces the following storage-level limits:

• Maximum number of tables per namespace: 500
• Maximum number of columns per table: 200

Free Plan

• Data-in: Rate of 5 MB per 5 minutes (average of 17 kb/s)
  • Uncompressed bytes of normalized line protocol
• Read: Rate of 300 MB per 5 minutes (average of 1000 kb/s)
  • Bytes in HTTP in response payload
• Available resources:
  • 2 buckets (excluding _monitoring and _tasks buckets)
• Storage:
  • Storage-level limits
  • 30 days of data retention (see retention period)

Usage-Based Plan

• Data-in: Rate of 300 MB per 5 minutes
  • Uncompressed bytes of normalized line protocol
• Read: Rate of 3 GB data per 5 minutes
  • Bytes in HTTP in response payload
• Unlimited resources
  • buckets
  • users
• Storage:
  • Storage-level limits
  • Set your retention period to unlimited or up to 1 year by updating a bucket’s retention period in the InfluxDB UI, or set a custom retention period using the influx bucket update command with the influx CLI.

Global limits

InfluxDB Cloud Serverless applies global (non-adjustable) system limits to all accounts, which protects the InfluxDB Cloud Serverless infrastructure for all users. As the service continues to evolve, we’ll continue to review these global limits and adjust them as appropriate.

Limits include:

• Write request limits:
  • 50 MB maximum HTTP request batch size (compressed or uncompressed–defined in the Content-Encoding header)
  • 250 MB maximum HTTP request batch size after decompression
• Query processing time: 90 seconds
• Total query time: 1500 seconds of total query time every 30 seconds
• Task processing time: 150 seconds
• Total task time: 1500 seconds of total task time every 30 seconds

Error messages when exceeding quotas or limits

Storage level Errors

Maximum number of columns reached

couldn't create columns in table `table_name`; table contains
<N> existing columns, applying this write would result
in <N+> columns, limit is 200

This error is returned for any write request that would exceed the maximum number of columns allowed in a table.

Potential solutions

• Consider storing new fields in a new measurement (not to exceed the maximum number of tables).
• Review InfluxDB schema design recommendations.
• Customers with an annual or support contract can contact InfluxData Support to request a review of their database schema.

Maximum number of tables reached

dml handler error: service limit reached: couldn't create new table; namespace contains <N> existing
tables, applying this write would result in <N+> columns, limit is 500

This error is returned for any write request that would exceed the maximum number of tables (measurements) allowed in a namespace.

Error messages in the UI

The InfluxDB Cloud Serverless UI displays a notification message when service quotas or limits are exceeded. The error messages correspond with the relevant API error response messages.

Errors can also be viewed in the Usage page under Limit Events–for example: event_type_limited_query, event_type_limited_write, or event_type_limited_delete_rate.

API error response messages

The following API error responses occur when your plan’s service quotas are exceeded.