influxdata / influxdata/influxdb

Influxdb2 full restore error: failed to restore TSM snapshot for shard XXX: 500 Internal Server Error

Open
#25,964 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area/2.x kind/bug
Dominant language
Rust
Stars
31.7k
Forks
3.7k
Avg merge
13h 37m
Merged PRs (30d)
8

Description

__Steps to reproduce:__

1. `influx backup --host --token --org '' /path/to/backup`

2. `influx restore --host --full --token /path/to/backup`

__Expected behaviour:__
Successful restore of db

__Actual behaviour:__
InfluxCLI fails on Error: failed to restore TSM snapshot for shard 10954: 500 Internal Server Error

__Environment info:__

K3s=1.31.3, Official influxdb:2.7.5 docker image.
Influx CLI dev (git: a79a2a1b825867421d320428538f76a4c90aa34c) build_date: 2024-04-16T14:34:32Z

__Config:__
DOCKER_INFLUXDB_INIT_MODE=setup
DOCKER_INFLUXDB_INIT_ORG=default
DOCKER_INFLUXDB_INIT_BUCKET=default
DOCKER_INFLUXDB_INIT_RETENTION=48h
INFLUXD_BOLT_PATH=/var/lib/influxdb2/influxd.bolt
INFLUXD_ENGINE_PATH=/var/lib/influxdb2
INFLUXD_SESSION_LENGTH=1440
INFLUXD_REPORTING_DISABLED=true
DOCKER_INFLUXDB_INIT_USERNAME=XXX
DOCKER_INFLUXDB_INIT_PASSWORD=XXX
DOCKER_INFLUXDB_INIT_ADMIN_TOKEN=XXX

__Logs:__

[influxdb2-restore-error.log](https://github.com/user-attachments/files/18655482/influxdb2-restore-error.log)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the `influx restore --full` command and inspect the attached `influxdb2-restore-error.log` alongside the backup and restore flow. Reproduce the failure in the stated K3s and InfluxDB 2.7.5 Docker environment, then verify that a full backup restores successfully without the TSM snapshot 500 error.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, kubernetes, rust
Domain
cli, databases
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.