-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Backups on Windows are failing due to boltdb issue #344
Comments
@dgnorton for prioritization |
Per Franco, this is happening on the latest docker image. |
This should only be happening if the CLI needs to build a manifest from a pre-2.1 Running CLI v2.2.1 with InfluxDB v2.1.1 on Windows 10 to do a backup works for me - doesn't need to create a legacy manifest like the log For backing up a 2.0.x The old CLI code didn't need to build a legacy manifest, but it did need to open the bolt file, as in: https://github.com/influxdata/influxdb/blob/d1233b7951ddf06a3f201c84f4b0915692c22ba5/backup/backup.go#L67 I believe the reason the old CLI code can do this on Windows is because it used the same logic to open the bolt file as the A simple fix for this error when backing up a legacy server on Windows therefor might be to not use the
I asked Franco in the community slack to confirm the version of |
From community slack:
See also underlying boltdb issue: etcd-io/bbolt#252
And #183 (comment)
Looks like we skipped a test on Windows and now its biting us. No movement on the upstream issue since Nov 2020 so we're going to have to find a workaround or fix the upstream I think.
The text was updated successfully, but these errors were encountered: