This release includes 3 breaking changes for platform teams planning a safe upgrade.
✓ No known CVEs patched in this version
Topics
+2 more
Affected surfaces
Summary
AI summaryUpdates Breaking Changes, Bug Fixes, and preview across a mixed release.
Full changelog
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-countrenamed to--pt-shard-count; there's no alias, so update startup scripts./api/v2/writereturns403(was401) for valid tokens lacking write permission; line-protocol parse errors now return400(was500).
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
Breaking Changes
- Catalog v3 migration is one‑way; back up `{prefix}/catalogs/` and `{prefix}/_catalog_checkpoint` before upgrading.
- `--pt-partition-count` renamed to `--pt-shard-count`; update startup scripts accordingly.
- `/api/v2/write` now returns 403 for tokens lacking write permission (was 401) and 400 for line‑protocol parse errors (was 500).
Weekly OSS security release digest.
The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.
No spam, unsubscribe anytime.
Share this release
Related context
Related tools
Beta — feedback welcome: [email protected]