InfluxDB automatic upgrade from 1.8.10 to 2.7.10 fails with "failed to find bucket with ID ..."

We are trying to upgrade InfluxDB 1.8.10 to 2.7.10 automatically according to the tutorial.
It fails with “bucket not found error”.
Please advise how we can resolve the issue :hammer_and_wrench:

OS:
Windows Server 2016 / 128Gb RAM / Intel Xeon E5-2680
-------------
InfluxDB:
- official binaries from: https://github.com/influxdata/influxdb/releases
- 317 databases in the old InfluxDB 1.8.10
-------------
Automatic upgrade command:
influxd upgrade --v1-dir "E:\influxdb\.influxdb" -m "E:\influxdb_27\.influxdbv2\influxd.bolt" -c "E:\influxdb_27\.influxdbv2\configs" --v2-config-path "E:\influxdb_27\.influxdbv2\config.toml" --engine-path "E:\influxdb_27\.influxdbv2\engine" --continuous-query-export-path "E:\influxdb_27\continuous_queries.txt" --log-path "E:\influxdb_27\upgrade.log" -b "some_db" -o "some_org" -r "0" -u "some_user" -p "some_password" -v
-------------
Run InfluxDB after upgrade command:
influxd run --flux-log-enabled --bolt-path "E:\influxdb_27\.influxdbv2\influxd.bolt" --engine-path "E:\influxdb_27\.influxdbv2\engine" --reporting-disabled
  1. Automatic upgrade works, but transfers not all the databases (let’s say a half).
    In the upgrade logs we see “bucket not found” error for each of the missing DBs:
{"level":"debug","ts":1727264460.1195505,"caller":"upgrade/database.go:61","msg":"Upgrading database","database":"some_db"}
{"level":"debug","ts":1727264460.1215525,"caller":"upgrade/database.go:78","msg":"Creating bucket","Bucket":"some_db/autogen"}
{"level":"debug","ts":1727264460.1215525,"caller":"tenant/middleware_org_logging.go:48","msg":"org find by ID","store":"new","took":0}
{"level":"debug","ts":1727264460.1255558,"caller":"tenant/middleware_bucket_logging.go:35","msg":"bucket create","store":"new","took":0.0040032}
{"level":"debug","ts":1727264460.1255558,"caller":"upgrade/database.go:86","msg":"Creating database with retention policy","database":"38695f7409b4ddfc"}
{"level":"info","ts":1727264460.1655476,"caller":"upgrade/database.go:101","msg":"Creating mapping","database":"some_db","retention policy":"autogen","orgID":"23b1e5dc2abdeb59","bucketID":"38695f7409b4ddfc"}
{"level":"debug","ts":1727264460.1665475,"caller":"tenant/middleware_bucket_logging.go:48","msg":"bucket find by ID","store":"new","took":0.0009999}
{"level":"debug","ts":1727264460.1675503,"caller":"tenant/middleware_bucket_logging.go:45","msg":"failed to find bucket with ID 0db63e5c6168b000","store":"new","error":"bucket not found","took":0}

Trying to find that bucket ID (0db63e5c6168b000) manually was unsuccessful. There is no such bucket in the “engine” folder of the new InfluxDB 2.7.10. Any other configurations of “influxd upgrade” command give the same result.

  1. Manual upgrade at the same time works for those missing databases.
    But in our case manual upgrade is not an option, because we have 317 databases.
    First of all, manual upgrade takes eternity to export/import.
    And moreover the database export file weighed !!! 750GB !!! for only 1 DB.

Thank you for any advice!

Hello @Alex_Zhurau,
I’m not sure. I would suggest creating an issue here: GitHub - influxdata/influxdb: Scalable datastore for metrics, events, and real-time analytics

Maybe there was an issue with the mapping?
Creates database and retention policy (DBRP) mappings required to query data with InfluxQL.

Can you

SHOW RETENTION POLICIES ON "database_name"

If a database is missing a retention policy, or if it is misconfigured, this could cause the “bucket not found” error. Fix any inconsistencies in the retention policies before retrying the upgrade.