InfluxDB

Developer Tools

The time-series data platform.

Latest v3.10.0 · by InfluxDataWebsiteinfluxdata/influxdb

Release activity

Release activity — 8 releases across 8 days in the last year. Each cell is one day; darker means more releases that day. Older weeks are hidden at this screen width.
MayJunJulAug
SundayNo releases on Apr 19, 2026No releases on Apr 26, 2026No releases on May 3, 2026No releases on May 10, 2026No releases on May 17, 2026No releases on May 24, 2026No releases on May 31, 2026No releases on Jun 7, 2026No releases on Jun 14, 2026No releases on Jun 21, 2026No releases on Jun 28, 2026No releases on Jul 5, 2026No releases on Jul 12, 2026No releases on Jul 19, 2026No releases on Jul 26, 2026No releases on Aug 2, 2026
MondayNo releases on Apr 20, 2026No releases on Apr 27, 2026No releases on May 4, 2026No releases on May 11, 2026No releases on May 18, 2026No releases on May 25, 2026No releases on Jun 1, 2026No releases on Jun 8, 2026No releases on Jun 15, 2026No releases on Jun 22, 2026No releases on Jun 29, 2026No releases on Jul 6, 2026No releases on Jul 13, 2026No releases on Jul 20, 2026No releases on Jul 27, 2026No releases on Aug 3, 2026
TuesdayNo releases on Apr 21, 2026No releases on Apr 28, 2026No releases on May 5, 20261 release on May 12, 2026No releases on May 19, 2026No releases on May 26, 2026No releases on Jun 2, 2026No releases on Jun 9, 2026No releases on Jun 16, 2026No releases on Jun 23, 2026No releases on Jun 30, 2026No releases on Jul 7, 2026No releases on Jul 14, 2026No releases on Jul 21, 2026No releases on Jul 28, 2026No releases on Aug 4, 2026
WednesdayNo releases on Apr 22, 2026No releases on Apr 29, 2026No releases on May 6, 2026No releases on May 13, 2026No releases on May 20, 2026No releases on May 27, 2026No releases on Jun 3, 2026No releases on Jun 10, 20261 release on Jun 17, 2026No releases on Jun 24, 2026No releases on Jul 1, 2026No releases on Jul 8, 2026No releases on Jul 15, 2026No releases on Jul 22, 2026No releases on Jul 29, 2026No releases on Aug 5, 2026
ThursdayNo releases on Apr 23, 2026No releases on Apr 30, 2026No releases on May 7, 2026No releases on May 14, 2026No releases on May 21, 2026No releases on May 28, 2026No releases on Jun 4, 2026No releases on Jun 11, 2026No releases on Jun 18, 2026No releases on Jun 25, 2026No releases on Jul 2, 2026No releases on Jul 9, 2026No releases on Jul 16, 2026No releases on Jul 23, 2026No releases on Jul 30, 2026No releases on Aug 6, 2026
FridayNo releases on Apr 24, 20261 release on May 1, 2026No releases on May 8, 2026No releases on May 15, 2026No releases on May 22, 2026No releases on May 29, 2026No releases on Jun 5, 2026No releases on Jun 12, 2026No releases on Jun 19, 2026No releases on Jun 26, 2026No releases on Jul 3, 2026No releases on Jul 10, 2026No releases on Jul 17, 2026No releases on Jul 24, 2026No releases on Jul 31, 2026No releases on Aug 7, 2026
SaturdayNo releases on Apr 25, 2026No releases on May 2, 2026No releases on May 9, 2026No releases on May 16, 2026No releases on May 23, 2026No releases on May 30, 2026No releases on Jun 6, 2026No releases on Jun 13, 2026No releases on Jun 20, 2026No releases on Jun 27, 2026No releases on Jul 4, 2026No releases on Jul 11, 2026No releases on Jul 18, 2026No releases on Jul 25, 2026No releases on Aug 1, 2026

8 releases in the last year

Changelog

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 originalPermalink
How v3.10.0 went

v2.9.1

Changed 1
  • Update Go to 1.25.10
Fixed 2
  • Level 3 compactions stop occurring
  • Split compaction queue depth from active running count

In addition to the list of changes below, please also see the official release notes for other important information about this release.

v2.9.1 [2026/05/11]

Bug Fixes
Maintenance
OSS BINARY FILESSHA256
influxdb2-2.9.1_darwin_amd64.tar.gz5b283ab29c8626a30debeee573c4508a304d46ffef417bae92be868ed0cc4782
influxdb2-2.9.1_linux_arm64.tar.gza99c3b89fc580f945a6d7a7b0b9c66961bb8b3bf9ddaaab1dae17cdf6af531c9
influxdb2-2.9.1_linux_amd64.tar.gz762e4fc825c4386e0c5138e7c3f91fc778081db2bada1ec47066e786bf55d9ff
influxdb2-2.9.1-windows_amd64.zipd8b93916a5e21fe348dfdb8de7ea04fb7425b38939486e874cd8096463b91043
OSS UBUNTU & DEBIAN PACKAGE FILESSHA256
influxdb2_2.9.1-1_amd64.deb1eeb9d9ef73e3c0f52b20697c2fe5f1304ecdae2d15cc3d272fc8b0f473fea24
influxdb2_2.9.1-1_arm64.deb6cb7859ed7a332e3efaf93551060ab7cde80f903ab61abe8c445267e820fcb68
OSS REDHAT & CENTOS PACKAGE FILESSHA256
influxdb2-2.9.1.x86_64.rpm897dc37a9e0d3366a46f379c523f6457e0562b5ab9c0c2f819b5ee1f04188e80
influxdb2-2.9.1.aarch64.rpm767983a4f6c3eadf2466ad8b97594173b5cf828f0ae2a3fca8587de41b4889b0
View originalPermalink
How v2.9.1 went
v2.9.0

V2.9.0

Added 4
  • Add gzip compression level configuration to backups
  • Add check for MaxAgeSeconds for EDR
  • Add CompactPointsPerBlock config option
  • Add retention policy scoped deletes to v1 queries
Changed 8
  • Improved config and env override handling
  • Port improved env overrides from master-1.x
  • Upgrade flux to v0.200.0 and go to 1.25.8
  • Update to go 1.24.13
  • Update go to 1.24.11
  • Cache generation and sequence to reduce TSM filename parsing
  • Modify optimized compaction holdoff to use debug logging
  • Modify optimized compaction to cover edge cases
Fixed 7
  • Existing iterators in a would leak reference counts
  • Return InfluxQL JSON marshaling errors correctly
  • Call findGenerations once per compaction plan
  • Reduce lock contention and races in purger
  • Handle nested low-level files in compaction
  • Full compactions not scheduled under some circumstances
  • Limit number of concurrent optimized compactions
Security 1
  • Enable token hashing by default

In addition to the list of changes below, please also see the official release notes for other important information about this release.

v2.9.0 [2026/05/01]

Bug Fixes
  1. fde85a2: Update GPG and build influx_tools in build
  2. fd1751f: Update security group to use default one for vpc
  3. 95c7f17: Existing iterators in a would leak reference counts
  4. cff46ca: Return InfluxQL JSON marshaling errors correctly
  5. a4f0220: Call findGenerations once per compaction plan
  6. dc9e5c8: Add rustlib path
  7. 124ca8f: Reduce lock contention and races in purger
  8. e071a23: Handle nested low-level files in compaction
  9. 103264e: Sort files for adjacency testing
  10. e3a77d4: Fix condition check for optimization of array cursor (tsm1)
  11. a50b420: Reduce unnecessary purger operations and logging
  12. 21c78b4: Full compactions not scheduled under some circumstances
  13. 3e19eed: Reduce excessive CPU usage during compaction planning
  14. 58fa2ab: Limit number of concurrent optimized compactions
  15. c0b35b7: PlanOptimize is running too frequently
  16. c4a18c8: Use correct path in open WAL error message
  17. ced2944: Correct locking bug when deleting a series
  18. e1a7cd3: Fix closing channel created twice in points writer (coordinator)
  19. e4c88be: Ignore empty index error deleting last measurement
  20. 4e7dcc4: Do not escape CSV output
  21. 54bf95c: Support absolute file paths in check-schema
  22. 38156bc: Series file index compaction
Features
  1. abb825b: Update UI release to OSS-v2.9.0
  2. a659d5f: Enable token hashing by default
  3. a74e111: Improved config and env override handling
  4. 533e9f7: Port improved env overrides from master-1.x
  5. 03d0dbb: Add check for MaxAgeSeconds for EDR
  6. d1deda2: Add gzip compression level configuration to backups
  7. b835658: Cleanup tasks bbolt entries during org deletion
  8. ba5455f: Adds nil check to SetNewReadersBlocked
  9. 0341909: Add CheckedClose test helper
  10. b6bc458: Upgrade flux to v0.200.0 and go to 1.25.8
  11. fa0ae4a: Adds logging when there are no shards during backup and restore
  12. ef1dd6b: Update rpm to use owned_dirs and update ci-packager-next
  13. 9a0b63b: Bubble error up to writer if fields are dropped
  14. 5bebb3e: Logging and fsync delay for retention deletion
  15. a38cc1f: Update to go 1.24.13
  16. 059d3de: Modify optimized compaction holdoff to use debug logging
  17. 2c4934f: Cache generation and sequence to reduce TSM filename parsing
  18. 6453347: Adds property based testing framework for compaction
  19. 25c2f56: Defer cleanup for log/index compactions, add debug log
  20. 70cef2c: Add new logging for compaction level 5 and remove bug with opt holdoff time
  21. afdbd16: Adds LastModifiedOrErr to expose error for LastModified
  22. 181d133: Add CompactPointsPerBlock config option
  23. 9a3dc55: Adds functionality to clear out bad shard list
  24. 1e4693a: Modify optimized compaction to cover edge cases
  25. 2ff5d01: Add retention policy scoped deletes to v1 queries
  26. 9f5e29f: Update go to 1.24.11
  27. 216beca: Extract meta.db from 2.x Bolt file
  28. ca05a4e: Update perf_test.sh to use different security group
  29. bf563c6: Update hardcoded subnet for perf-test.sh
Other
  1. cd043ba: Chore: bump github.com/jackc/pgx/v5 from 5.8.0 to 5.9.2
  2. 288e524: Chore: update to go 1.25.9
  3. 79f5bf9: Docs: update v2 README for clarity and version context
  4. 19f0cd6: Chore: reduce string allocations in TSI series cache
  5. f67d857: Chore: improve logging on compaction failures
  6. eb8c4e6: Chore: remove TokenMigrator and related code
  7. d89cf61: Chore: CI improvements
  8. 1729869: Chore: add authorization store constructor options
  9. 6b045f4: Chore: add shard to compaction logging as in 1.X
OSS BINARY FILESSHA256
influxdb2-2.9.0_darwin_amd64.tar.gz228c09f5addb2b7bb0fea083f9f0e3cad2368627fa4f75f8f8dda83115063443
influxdb2-2.9.0_linux_arm64.tar.gz8926b0f379ea9985de2962154b50c4a84a8554af3e33759cf79f873bd8ab9673
influxdb2-2.9.0_linux_amd64.tar.gz47c1dd33e712357425ad56bfaf0d11082d379862e301a88b32ada1d705853aac
influxdb2-2.9.0-windows_amd64.zip91647df8a6f6e39bb1a8ab067b93848804bbf1c55ecd375c09bb75d99945d2f8
OSS UBUNTU & DEBIAN PACKAGE FILESSHA256
influxdb2_2.9.0-1_amd64.debfc5b133d1407c03c7af5f730369c189ad8b6f27a202e5882906ee5753b2ef751
influxdb2_2.9.0-1_arm64.deba883ceb8da64d77169413c7a43cc6f12516d6b42a0296c2b4dcaa1f201ed758a
OSS REDHAT & CENTOS PACKAGE FILESSHA256
influxdb2-2.9.0.x86_64.rpm34536f53170a915d2cef8471a196fcf076fd30482ef26a5dd7da461b4e6ff888
influxdb2-2.9.0.aarch64.rpme757020c71bd86bd56c14a78ae741b20ad1757fd266987d572471ce81866afae
View originalPermalink
How v2.9.0 went

v1.12.4

Fixed 1
  • Fixed fatal error: concurrent map iteration and map write panic in the TSI index that could crash InfluxDB during concurrent read and write operations
Bug Fixes
  • Fixed fatal error: concurrent map iteration and map write panic in the TSI index that could crash InfluxDB during concurrent read and write operations. This was a regression introduced in v1.12.3. The fix restores the original locking behavior.

OSS BINARY FILESSHA256
influxdb-1.12.4_linux_amd64.tar.gz6c55e15f72321eaff39b9ae1bc8a113082be07045fb4086e481f828af07ddb99
influxdb-1.12.4_linux_arm64.tar.gz706437afe29c07e0c86ed4a454fa0cbf621be2cf472a1e7eb146628745a5ced3
influxdb-1.12.4_darwin_amd64.tar.gz3369f7ae0fbb8ff1d4fec136d3ea581573403fb17ccad9f8df606e364796adc3
influxdb-1.12.4-windows_amd64.zip886332f494e80406b542d0a2a4a7cc5be98f08f8a9f8e651beed695eca9597e6
OSS UBUNTU AND DEBIAN PACKAGE FILESSHA256
influxdb_1.12.4-1_amd64.deb39362452cfd9584603e96c185d88b561fa45bc7078e5dbef3a3311b81c45cb5b
influxdb_1.12.4-1_arm64.debf64f50fdfb9c36e63f8628186ec273b55e2f8e065c46433ac59e35982d4ec99e
OSS REDHAT & CENTOS PACKAGE FILESSHA256
influxdb-1.12.4.aarch64.rpm47346f4085538d8c36adf023664017ed78b469bf28b44326e9606187d3d06ad6
influxdb-1.12.4.x86_64.rpm87261d54f7f5eb2af2a2fb4de26bb53110f7f40f459b15f1b1900d5cd6a78e75
View originalPermalink
How v1.12.4 went
v3.9.0

v3.9.0 | 04-02-26

Added 1
  • Product identity in HTTP responses, metrics, HTTP response headers, and metadata now distinguish between Core and Enterprise builds
Changed 2
  • Upgrade the embedded DataFusion query engine to DF 51 for more efficient query execution
  • Update the bundled Python runtime for processing engine plugins with the latest security and bug fixes
Fixed 1
  • Background resources such as processing engine triggers are now cleanly decommissioned when a database is removed

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

Note: This is the first GitHub "release" in a while (since 3.4.0), however there have been many releases since then; you can find those additional notes in the Release Notes as well to learn about all of what has been updated. These changes reflect the differences between 3.8.4 and 3.9.0.

Updates

DataFusion upgrade: Upgraded the embedded DataFusion query engine to DF 51 for more efficient query execution.

Python runtime upgrade: Updated the bundled Python runtime for processing engine plugins with the latest security and bug fixes.

Product identity in HTTP responses: Metrics, HTTP response headers, and metadata now distinguish between Core and Enterprise builds.

Database lifecycle hardening: Background resources such as processing engine triggers are now cleanly decommissioned when a database is removed.

Bug Fixes
  • Several bug fixes and performance improvements

Full Changelog: https://github.com/influxdata/influxdb/compare/v3.8.3...v3.9.0

View originalPermalink
How v3.9.0 went

v1.12.3

Added 4
  • Use zap.AtomicLevel for dynamic logging levels
  • Add time_format param for httpd
  • Add TLS certificate reloading on SIGHUP
  • Add client certificate support to TLSCertLoader
Changed 1
  • Update to Go 1.23.12
Fixed 16
  • Fix CI to build arm64 artifacts
  • Add locking in ClearBadShardList
  • Stop noisy logging about phantom shards that do not belong to node
  • Resolve RLock() leakage in Store.DeleteSeries()
  • Fix condition check for optimization of array cursor (tsm1)
  • init.sh should run buildtsi as influxdb user

In addition to the list of changes below, please also see the official release notes for other important information about this release.

v1.12.3 [2026/01/12]

Bug Fixes
  • 3d4f3a2: Fix CI to build arm64 artifacts
  • 1141c66: Fix package publishing to fix Slack msg & publish_packages
  • e8ef25b: Add locking in ClearBadShardList
  • c168cc5: Stop noisy logging about phantom shards that do not belong to node
  • 21ab484: Resolve RLock() leakage in Store.DeleteSeries()
  • 31cb61f: Fix condition check for optimization of array cursor (tsm1)
  • 70543be: init.sh should run buildtsi as influxdb user
  • e883e8b: Reduce unnecessary purger operations and logging
  • 7f56ad3: Sort files for adjacency testing
  • fe1bc35: Fix operator in host detection (systemd)
  • 39c1b0a: Use correct path in open WAL error message
  • d1d68d6: Handle nested low-level files in compaction
  • 52cd83d: Correct error logic for writing empty index files
  • d5a48e0: Reduce lock contention and races in purger
  • 2b71644: Fix bug with authorizer leakage in show queries
  • 82729cf: Rename compact throughput logging keys
  • ba705ec: Fix https-insecure-certificate not handled properly in httpd
  • 5e9d85c: Prevent level regression when compacting mixed-level TSM files
Features
  • a743838: Use zap.AtomicLevel for dynamic logging levels
  • 31b41a6: Improve dropped point logging
  • 133c290: File store merge metrics
  • b9a0155: Add time_format param for httpd
  • bd3eb34: Add LastModifiedOrErr to expose error for LastModified
  • e51acc4: TagValueIterator holds RLock for too long - performance improvement
  • 269f1b6: Add 'config' to 'debug/vars' http endpoint
  • ba2c2b6: Add property-based testing framework for compaction
  • f748c5c: Defer cleanup for log/index compactions, add debug log
  • 0e656d6: Add statistics measurement for compact-throughput
  • f75be56: Add 'cq' diagnostics to /debug/vars
  • f0d5c73: Cache generation and sequence to reduce TSM filename parsing
  • 439604e: Modify optimized compaction holdoff to use debug logging
  • 32d8b00: Show user when displaying or logging queries
  • 1356a21: Bubble error up to writer if fields are dropped
  • aa1775b: Add TLS certificate reloading on SIGHUP
  • bac5ced: Update Stream to accept a bufSize for tar CopyBuffer window
  • a2e029f: Add access-log-status-filters to default influxd config output
  • e3b0586: Add client certificate support to TLSCertLoader
  • 1420aaf: Logging and fsync delay for retention deletion
  • 4dcc877: Report user query bytes
  • 049b1f7: Add TLSConfigManager
  • 0f3436d: Add CheckedClose test helper
  • 7f42c16: Updates post-install for linux package builds
Other
  • 0a4c903: Update to Go 1.23.12
  • 88c1c31: Enable Windows and Apple builds in CI
  • d0c94e9: Build Windows and Darwin packages in CI
  • 61d9216: Bump golang.org/x/oauth2 from v0.21.0 to 0.27.0
  • 12b46eb: Update CHANGELOG link
  • d8ecd34: Revert release to use version sub-directory
  • 55b7fb5: Update Go toolchain to 1.23.12
  • d628f8b: Add influxdata-archive-keyring package
  • 542ce7f: Update Go to 1.24.9
  • 56a3f97: Update Go to 1.24.11
  • 1a6880b: Update Go mod to 1.24.11
  • d65673b: Update to Go 1.24.13
  • 6a3b02c: Use new cache, add rustlib path in CI
  • f3d5cb6: Reduce string allocations in TSI series cache

OSS BINARY FILESSHA256
influxdb-1.12.3_linux_amd64.tar.gz5649b7d4b6c4ececd98d3438719300dbf9692c3139e201df1f32fe4b03466cd7
influxdb-1.12.3_linux_arm64.tar.gzbba94ae038e4330dd8f17f586d2f52b2ef5d994950cf294e7027d3621f6836f6
influxdb-1.12.3_darwin_amd64.tar.gz8ffbc5066aa13a238e52f6af5e4c8091670d8e52c704dff8499a23aebe5fe3ce
influxdb-1.12.3-windows_amd64.zip98cf24159e99c210d3812295c8b553aa732072e6c965b20b5d8bd97fa77a005b
OSS UBUNTU AND DEBIAN PACKAGE FILESSHA256
influxdb_1.12.3-1_amd64.debfb6ca0e461063054456a5084dc878161880736c5af3677ef23f7837848f3e6b5
influxdb_1.12.3-1_arm64.debd38e78b2fc40452788ded105f29b76aee673018cd410171897d9f07da01a7c9b
OSS REDHAT & CENTOS PACKAGE FILESSHA256
influxdb-1.12.3.aarch64.rpm7f3dc2be50b349dbbda53a5e79bf7c92e7fc03a39e5035c358b6a5b0c21031ec
influxdb-1.12.3.x86_64.rpm4478f452e9ff8acf125aef9a71d3117d37b9ddd9ddaef13371cf4ee9f710910d
View originalPermalink
How v1.12.3 went

v2.8.0

Added 1
  • Add optional token hashing via --use-hashed-tokens flag to store API tokens as hashes on disk
Changed 1
  • Update Go to 1.24.9
Fixed 1
  • Fix compilation on alpine linux

In addition to the list of changes below, please also see the official release notes for other important information about this release.

v2.8.0 [2025/12/12]

Bug Fixes
  1. 305e61d: Fix compilation on alpine linux
Features
  1. 5e204dc: Add optional token hashing
Token Hashing

InfluxDB OSS 2.8.0 introduces token hashing. When activated using the --use-hashed-tokens, all API tokens are stored as hashes on disk. While token hashing is a valuable security upgrade, care should be taken when upgrading and enabling token hashing.

Documentation link: use-hashed-tokens

It is highly recommended to upgrade to 2.8.0 or later versions and enable hashed tokens in two steps, not one.

How Token Hashing Works

Upon upgrading to version 2.8.0 or later releases from version 2.7.12 or earlier releases, the BoltDB schema is upgraded to add a new index bucket.

Upon startup when token hashing is enabled, all unhashed tokens are converted to hashed tokens and unhashed tokens are deleted. This check and conversion of unhashed tokens occurs on every startup when token hashing is enabled.

When token hashing is disabled, any new tokens are stored as hashed tokens. If token hashing is disabled after being disabled, newly created tokens are stored unhashed. However, existing tokens remain hashed on disk.

Hashed Tokens Are Lost During Downgrade

Be aware that once token hashing is enabled, downgrading to a version earlier than 2.8.0 will erase all API tokens due to the required schema downgrade. This means downgrading requires recreating all API tokens and updating them on clients. Even if token hashing is disabled before downgrading, all API tokens will still need to be recreated because disabling token hashing does not unhash tokens stored in hashed form.

If token hashing is never enabled, then it is possible to downgrade from 2.8.0 to 2.7.12 and earlier.

Recommended Process

It is not necessary to enabled token hashing immediately after upgrading. Token hashing is also not required by 2.8.0.

  1. Upgrade InfluxDB.
    1. Initiate influxd shutdown.
    2. Wait for a clean shutdown.
    3. Upgrade influxd.
    4. Start influxd.
  2. Verify upgrade is successful.
  3. Enable Token Hashing (if desired)
    1. Initiate influxd shutdown.
    2. Wait for a clean shutdown.
    3. Update configuration to use token hashing by adding --use-hashed-tokens to the command line or INFLUXD_USE_HASHED_TOKENS=true to the container environment. Or set use-hashed-tokens to true in the configuration file.
    4. Start influxd.
Other
  1. 1e14c08: Update Go to 1.24.9
  2. 40a6332: Updates post-install for linux package builds
OSS BINARY FILESSHA256
influxdb2-2.8.0_darwin_amd64.tar.gzab08199474f26c2feb636b993b1aaa3b159b9d849d0e66a69a812af193a042ec
influxdb2-2.8.0_linux_arm64.tar.gz263196a8970ceea2d8ff4b90c85555b7573a86c9d83f797a8dfc136e554edd70
influxdb2-2.8.0_linux_amd64.tar.gzdf28cb9d3cb47732908604d963b20271a3fb0e83f418976cc482f991e328957d
influxdb2-2.8.0-windows.zip464d1240a7764c1c024021b5c5ac4a9943570929d615beec83a12f5e793becae
OSS UBUNTU & DEBIAN PACKAGE FILESSHA256
influxdb2_2.8.0-1_amd64.deba4f2bcbf858ea664136c83faf603aa694edef4d1a54b11ad8305126fd77e9142
influxdb2_2.8.0-1_arm64.debb0a5326a3ecaad20176528dd7404a3b262bb59a9eae15095fb5f2bab085e2757
OSS REDHAT & CENTOS PACKAGE FILESSHA256
influxdb2-2.8.0.x86_64.rpmfc5cdb6d3fdec1d8b4d0e3130cb424ea14dbf88da4de8d88666aa4bc87adfc57
influxdb2-2.8.0.aarch64.rpmf53d82e0f2b2a60b941ba3119f42b444a9a840e0d956dfa9e2cb0876eef7952d
View originalPermalink
How v2.8.0 went
v3.4.0

v3.4.0 | 08-26-25

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

Updates

Token Provisioning: You can now generate authentication tokens offline that can then be loaded up by the database at runtime if the tokens do not already exist, which works great for automated deployments and containerized environments. (#26734)

Azure Endpoint: You can now specify the Azure endpoint for object-store connections using the --azure-endpoint parameter (#26687)

No_Sync via CLI: The no_sync option can now be specified with the --no-sync parameter via the CLI on write commands (#26703)

Bug Fixes
  • Tag and field names are validated when creating tables (#26641)
  • Using GROUP BY twice on the same column no longer causes incorrect data (#26732)
Security & Misc
  • Overly verbose TableIndexCache log is now quiet (#26709)
  • WAL replay concurrency limit now defaults to number of CPU cores, preventing possible OOM (#26715)
  • Unsafe signal_handler code removed (#26685)
  • Python version upgraded to 3.13.7-20250818 (#26686, #26700)

Full Changelog: https://github.com/influxdata/influxdb/compare/v3.3.0...v3.4.0

View originalPermalink
How v3.4.0 went
v3.3.0

v3.3.0 | 07-30-25

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

Updates

Authentication and security: Add admin token recovery server that allows regenerating lost admin tokens without existing authentication. Includes new --admin-token-recovery-http-bind option for running recovery server on separate port, with automatic shutdown after successful token regeneration (#26594)

Process Engine Trigger Arguments: You can access the trigger arguments for Process Engine triggers using the system.processing_engine_trigger_arguments table [#26604]

Passing git hash via env: Using environment variables, you can now pass the git hash in build.rs [#25266]

Fixes

Database reliability:

  • Fix URL encoded table name handling failures (#26586)

  • Allow hard deletion of existing soft-deleted schema (#26574)

Authentication: Fix AWS S3 API error handling when tokens are expired (#1013)

Query processing: Set nanosecond precision as default for V1 query API CSV output (#26577)

CLI reliability:

  • Mark --object-store CLI argument as explicitly required (#26575)
  • Add help text for the new update subcommand (#26569)
New Contributors

Full Changelog: https://github.com/influxdata/influxdb/compare/v3.2.1...v3.3.0

View originalPermalink
How v3.3.0 went
View all

Discussion