influxdata / influxdata/influxdb

InfluxDB Restore data too much slow

Open
#24,370 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Rust
Stars
31.7k
Forks
3.7k
Avg merge
13h 37m
Merged PRs (30d)
8

Description

Hello everyone,

We are using InfluxDBv2 OSS on docker .
We have problems with the restores of the backups.
Firstly, we have tried to do the backups completely: **influx backup -t --token** , but the restore was extremely slow and the server froze

Then, we changed the method and we started to do the backups by bucket: **influx backup --bucket -t --token**. However, the restore was extremely slow and the server froze too.

The backup apparently works correctly and fast without problems, but the restore of the backup is our problem. We tried only restore one bucket and we did with one that store about 65-70GB of data, but when we apply the command 'influx backup --bucket ...' it turns in about 2-2.5GB. It is getting days of restoring so i think it smells weird.

On the other hand we tried with one bucket that appling the command 'influx backup --bucket it store 400-500MB and when we start the restore of the bucket it works correctly and fastly.

We are doing the restore in one server with about 1TB SSD, 16GB RAM, i5.

We will continue trying other methods while we wait a response about this :S.

Please watch the next picture where you can see the time spent in the last shard. The time that need each shard is incremented with each shard restored. Any idea about this problem?
![github](https://github.com/influxdata/influxdb/assets/60984280/3d964309-c73a-496d-a48a-3e9e449b9773)

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the reported `influx backup --bucket` restore with the 65–70GB bucket and the smaller 400–500MB bucket on the stated 1TB SSD, 16GB RAM server. Compare the shard timing shown in the attached image and record whether the server freezes; the issue is resolved when the large backup restores without progressively increasing shard times or days-long execution.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker
Domain
databases
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.