Upgrade InfluxDB 3 Core
Upgrade your InfluxDB 3 Core version.
Before you upgrade
Before upgrading your InfluxDB 3 Core instance, review the release notes for compatibility requirements and then plan your upgrade strategy.
Upgrading to InfluxDB 3.10 is a one-way migration
The first time you start InfluxDB 3.10, it automatically upgrades the on-disk catalog format from v2 to v3. After migration, 3.9.x and older binaries are unable to read the new catalog, and fail to start on the same cluster data.
Before upgrading, back up {prefix}/catalogs/ and {prefix}/_catalog_checkpoint.
Restoring these objects is the only way to roll back to 3.9.x.
Upgrading to InfluxDB 3.12 removes rollback to any 3.11.x release
InfluxDB 3.12 adds a catalog record type that 3.11.x binaries can’t read. Once every running node in the cluster is on 3.12 (which happens at first startup on a single node), the catalog commits the new feature level. From then on, a 3.11.x binary refuses to load the catalog and reports that the node’s feature level is below the cluster’s committed level. This applies to InfluxDB 3 Core whether or not you use any of the features that require it.
Back up everything under {prefix}/catalog/ (the catalog snapshot and
logs under catalog/v3/) before you upgrade.
Restoring these objects is the only way to roll back to 3.11.x.
Other changes to review before you upgrade to 3.12
- Query concurrency now has a finite default:
--max-concurrent-queriesdefaults to the larger of50and 4 times the node’s query parallelism, instead of being effectively unlimited. Queries submitted over the limit wait for a slot instead of running immediately. - The WAL buffer limit is now enforced:
--wal-max-buffered-writes(default100000) previously had no effect. Once the WAL buffer fills, writes now return429 Too Many Requestsuntil it drains. - HTTP and gRPC request metrics are split by protocol:
http_requests*metrics now count only HTTP requests, andgrpc_requests*metrics count only gRPC requests. Dashboards that summed the two families report lower values after you upgrade. Thepathandmethod_pathlabels are now route templates, such as/api/v3/engine/:path, instead of literal paths; update panels that filter on a specific path.
For the complete list of changes, see the release notes.
Verify your current version
Before upgrading, verify the InfluxDB 3 Core version running on each node.
influxdb3 --versiondocker exec CONTAINER_NAME influxdb3 --versionReplace the following:
CONTAINER_NAME: The name of your InfluxDB 3 Core container
The command returns version information similar to the following:
influxdb3 3.12.0Verify your InfluxDB version
Before and after upgrading, verify the InfluxDB 3 Core version running on your instance.
Upgrade an InfluxDB 3 instance
curl -O https://www.influxdata.com/d/install_influxdb3.sh \
&& sh install_influxdb3.sh core# 1. Download the new version
curl -L https://dl.influxdata.com/influxdb/releases/influxdb3-core-3.12.0_linux_amd64.tar.gz \
-o influxdb3-core.tar.gz
# 2. Extract the archive
tar xvzf influxdb3-core.tar.gz
# 3. Stop the service
sudo systemctl stop influxdb3-core
# 4. Install the new binary
sudo cp influxdb3 /usr/local/bin/
# 5. Start the service
sudo systemctl start influxdb3-coredocker stop CONTAINER_NAME
docker pull influxdb:core
docker start CONTAINER_NAMEReplace the following:
CONTAINER_NAME: The name of your InfluxDB 3 Core container
docker compose down
docker compose pull
docker compose up -d# Download the latest Windows binary
Invoke-WebRequest `
-Uri "https://dl.influxdata.com/influxdb/releases/influxdb3-core-3.12.0-windows_amd64.zip" `
-OutFile "influxdb3-core.zip"
# Extract the binary
Expand-Archive -Path influxdb3-core.zip -DestinationPath . -Force
# Stop the service, replace the binary, and start the service
Stop-Service influxdb3
Copy-Item -Path "influxdb3.exe" -Destination "C:\Program Files\InfluxData\influxdb3\" -Force
Start-Service influxdb3Was this page helpful?
Thank you for your feedback!
Support and feedback
Thank you for being part of our community! We welcome and encourage your feedback and bug reports for InfluxDB 3 Core and this documentation. To find support, use the following resources:
Customers with an annual or support contract can contact InfluxData Support.