InfluxDB v3.10.0

v3.10.0

v3.10.0 | 06-17-26

Added 11
  • Catalog v3 automatically migrates to a compact binary format on first startup, reducing catalog size by approximately 5–6x compared to v2
  • Processing engine supports cross-database queries via the `database=` keyword argument on `influxdb3_local.query()`
  • Processing engine has trigger lockdown with new serve flags `--restrict-plugin-triggers-to` and `--plugin-dir-only` to restrict plugin behavior
  • GET /ready endpoint returns 200 OK when the server can reach object storage and 503 when it cannot
  • Always-on heap profiling enabled at startup with negligible overhead accessible at the pprof endpoint
  • influxdb3 debug catalog command allows inspecting catalog state offline directly from object storage without a running server
Changed 4
  • Object-store licenses are no longer bound to object-store config allowing bucket or store migration with the same license
  • `--pt-partition-count` flag renamed to `--pt-shard-count` with no alias
  • `/api/v2/write` endpoint now returns 403 for valid tokens lacking write permission instead of 401
  • Line-protocol parse errors on `/api/v2/write` now return 400 instead of 500
Fixed 1
  • Compaction stability improvements including ingest-time, deadlock, write-amplification, and gen1 orphaning fixes

The following are some highlighted updates with the newest release for InfluxDB 3 Core and Enterprise. Learn more via our full Release Notes.

InfluxDB 3 Core Updates

Catalog v3: The on-disk catalog automatically migrates to a compact binary format (~5–6x smaller than v2) on first startup. Migration is automatic, idempotent, and crash-safe. Back up {prefix}/catalogs/ and {prefix}/_catalog_checkpoint before upgrading; the migration is one-way and 3.9.x binaries cannot read a v3 catalog.

Processing engine supports cross-database queries: Plugins can now read from any database using the database= keyword argument on influxdb3_local.query().

Processing engine now has trigger lockdown: New serve flags restrict plugin behavior; --restrict-plugin-triggers-to limits triggers to wal, schedule, or request, and --plugin-dir-only

GET /ready endpoint: Returns 200 OK when the server can reach object storage, 503 when it cannot; ideal for load balancer and orchestration readiness probes.

Always-on heap profiling: Enabled at startup with negligible overhead (~<1% CPU), accessible at the existing pprof endpoint. Disable with MALLOC_CONF=prof:false.

influxdb3 debug catalog: Inspect catalog state offline directly from object storage; no running server required.

InfluxDB 3 Enterprise Updates

All Core updates are included in Enterprise. The following are exclusive to Enterprise. Many of these require the new performance update preview (in beta); if using these features, they should not be included in production environments yet.

Row-level deletion: Delete rows by time range and tag predicates with influxdb3 delete rows. Deletion is asynchronous and applied by the compactor. Monitor with the system.row_deletes table. Requires --use-pacha-tree.

Backup and restore: Full backup and restore management via new influxdb3 create/status/show/delete/cancel backup and restore commands, plus matching /api/v3/enterprise/backup and /restore endpoints. Requires --use-pacha-tree and a compactor node with an admin token.

Bulk import: Import generic (non-IOx) Parquet files with influxdb3 import upload, mapping columns to InfluxDB types via --column flags. Track jobs with influxdb3 import list.

User auth and RBAC (preview): Multi-user authentication with username/password → JWTs, optional OAuth/OIDC, and three built-in roles (Admin, Auditor, Member). Off by default (--without-user-auth true).

Object-store license portability: Licenses are no longer bound to object-store config (type, bucket, endpoint, region) — validation enforces only signature, expiry, and licensed core count. You can move buckets or stores with the same license.

Observability: 36 new influxdb3_compactor_* Prometheus metrics, with influxdb3_compactor_snapshot_lag_seconds as the primary health signal.

Breaking Changes
  • Catalog v3 migration is one-way: Back up your catalog before upgrading (see above).
  • --pt-partition-count renamed to --pt-shard-count; there's no alias, so update startup scripts.
  • /api/v2/write returns 403 (was 401) for valid tokens lacking write permission; line-protocol parse errors now return 400 (was 500).
Bug Fixes
  • Compaction stability improvements (ingest-time, deadlock/write-amplification, gen1 orphaning, and upgrade-blocking fixes), plus several other bug fixes and performance improvements.

  • Many other bug fixes and performance improvements

Full Changelog: https://github.com/influxdata/influxdb/compare/v3.9.3...v3.10.0

View original

Upgraded? How did it go?

Discussion