influxdata / influxdata/influxdb
Backup removes shards
- Dominant language
- Rust
- Stars
- 31.7k
- Forks
- 3.7k
- Avg merge
- 13h 37m
- Merged PRs (30d)
- 8
Description
__Steps to reproduce:__
List the minimal actions needed to reproduce the behavior.
1. Login on debian as root and run `influx backup /tmp/backup_test1 -t "MyToken"`
__Expected behavior:__
All data should be back upped in given location
__Actual behavior:__
A lot of warnings ala `WARN: Shard XY removed during backup`

__Environment info:__
* System info: Linux 5.10.0-19-amd64 x86_64 (Debian 11)
* InfluxDB version: InfluxDB v2.5.0 (git: 6fc66acb0a) build_date: 2022-11-01T16:55:44Z
__Config (/etc/influxdb/config.toml):__
```
bolt-path = "/var/lib/influxdb/influxd.bolt"
engine-path = "/var/lib/influxdb/engine"
http-bind-address = ":8086"
```
There is a bug report on influxdata-docker for this (https://github.com/influxdata/influxdata-docker/issues/604) but I'm running no docker. So I reckon its a core influxdb problem
It kinda shocks me! How can such a crutial thing like backup and restore your data be faulty? Isn't there a unit test to cover this?
Contributor guide
Research direction
Reproduce the issue with `influx backup /tmp/backup_test1 -t "MyToken"` on Debian using the provided InfluxDB 2.5.0 environment and configuration. Inspect the backup and shard-removal warnings, then compare the result with the expected complete backup. Done means the backup completes without removing shards and includes all data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, rust
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100