influxdata/influxdb v3.10.6

v3.10.6 | 09-04-26

on GitHub

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

Core

Features

• --shutdown-timeout graceful shutdown bound: This new option (default 30s) caps how long the server waits for active connections to drain during shutdown before forcibly closing them. Set it to 0s to skip the drain.

Bug fixes

• Crash loop migrating a catalog written by Core: Catalog snapshots deserialize again when the node spec is missing from trigger, last value cache, and distinct value cache entries, defaulting to all nodes. Core never writes that field, so the unified deserializer rejected Core-written checkpoint files and the v2-to-v3 catalog migration crash-looped on upgrade.
• Snapshot manifest skipped for an empty snapshot: Every snapshot sequence number now lands a manifest, including a snapshot with nothing to persist. Previously the manifest was skipped, leaving a permanent hole in the sequence. Consumers that walk the sequence by exact key cannot tell a skipped snapshot from a manifest that failed to persist, so a single hole stalled Enterprise compaction on that node and blocked its read replicas.
• Unnecessary node shutdown after a retried WAL write: Each WAL file now carries a nonce in its object metadata, so a node recognizes its own write and shuts down only for a file written by another node. Previously, a conditional PUT that was applied but returned a 500 was retried, and the node read the resulting 412 as a second process holding the same --node-id and shut down, though the file was durable and correct.
• Panic on oversized duration values: Time arithmetic now saturates at the minimum or maximum representable timestamp instead of panicking when a duration is too large to represent. Previously, an oversized user-supplied duration produced a panic and could put the server into a startup panic loop.
• Processing engine Python updated to 3.13.15: Picks up the security fixes in that release.
• Other bug fixes and performance improvements

Enterprise

All Core updates are included in Enterprise.
Additional Enterprise-specific updates:

Features

• Startup phase logging: The server logs the start and completion of each startup phase, so a node killed during startup shows which phase it was in.

Bug fixes

• Privilege escalation through role assignment: Creating, updating, and deleting a role, and assigning roles to a user, now require admin authorization. Previously a non-admin subject holding User:Update, or User:Create with roles in the request, could grant permissions beyond its own. This affects the user authentication preview, which is off by default (--without-user-auth true); deployments that have not enabled it are unaffected.
• File index left behind when a generation expires: Retention now deletes a generation's detail object along with its Parquet files. Previously the detail, which holds the file index describing those files, was left unreferenced in object storage. On a table with high-cardinality index columns the detail is the larger of the two, so retention shrank the data and accumulated the indexes for the life of the cluster.
• Slow compaction catch-up behind a lagging node: The compactor now accumulates the rerun signal across every node in a cycle. Previously it kept only the last node's value, so a caught-up node could end the cycle after a single snapshot and leave a lagging node advancing one snapshot per check interval until restart.
• Other bug fixes and performance improvements