Skip to content
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

InfluxDB 2.4.0 not able to take the backup properly for few buckets. #25120

Open
ravi9717 opened this issue Jul 1, 2024 · 6 comments
Open

InfluxDB 2.4.0 not able to take the backup properly for few buckets. #25120

ravi9717 opened this issue Jul 1, 2024 · 6 comments
Assignees
Labels
area/2.x OSS 2.0 related issues and PRs team/edge

Comments

@ravi9717
Copy link

ravi9717 commented Jul 1, 2024

Steps to reproduce:
List the minimal actions needed to reproduce the behavior.

  1. create multiple orgs and one default org with different tokens and different bucket names
  2. create multiple buckets in each org and set different data retention policies for different buckets but the same across various orgs
  3. Now try to create the backup for different buckets across different orgs using the default org token

Expected behaviour:
Influx backup -o org -b bucket -t token path should create the backup for the bucket for all buckets in all orgs

Actual behaviour:
It creating the backup randomly for different buckets across different orgs

Environment info:

  • Please provide the command you used to build the project, including any RUSTFLAGS.
  • System info: ubuntu 20.04, 64 CPU, 512 Memory, 46 GB root storage available, CPU and memory utilization more then 10-20 %
  • InfluxDB 2.4.0 docker container, Influx CLI 2.4.0 (git: 5c7c34f) build_date: 2022-08-18T19:26:48Z

Config:
Copy any non-default config values here or attach the full config as a gist or file.

Logs:
this is the log of the bucket for which we able to create the backup
image (1)

this is the logs of the bucket for which we are not able to create the backup, it just only shows downloading the metadata after that it stops.
image (2)

@ravi9717
Copy link
Author

ravi9717 commented Jul 1, 2024

I have observed one more thing even if I pass the wrong bucket name in the command it doesn't give any error it simply shows downloading the metadata if other than token something else is wrong it's not showing in the command output.

@davidby-influx
Copy link
Contributor

Can you send the exact commands to reproduce the problem, using only the influx CLI?

Start with influx setup

Then the commands to create the organizations and buckets, and finally the back-up command.

I will be attempting to reproduce on v2.7, not v2.4, so it might be worthwhile for you to upgrade, as well.

@davidby-influx davidby-influx self-assigned this Jul 8, 2024
@davidby-influx davidby-influx added area/2.x OSS 2.0 related issues and PRs team/edge labels Jul 8, 2024
@ravi9717
Copy link
Author

I have created all the buckets from the InfluxDB GUI.

data retention for the bucket I configured from the CLI

influx backup -o org -t token -b bucket_name path

@ravi9717
Copy link
Author

I have observed one more thing even if I pass the wrong bucket name in the command it doesn't give any error it simply shows downloading the metadata if other than token something else is wrong it's not showing in the command output.

Please re-produce this issue as well

@davidby-influx
Copy link
Contributor

@ravi9717 - If you can provide a CLI script to reproduce the problem, we can take a look at it. But without the exact bucket names, retention periods, data inserted, etc, we will be unable to experiment to see if we can reproduce the problem.

@ravi9717
Copy link
Author

what I have observed with my data is that this issue doesn't depend on the bucket name or the data type or data retention.

Because we are running the InfluxDB with multiple orgs and we have multiple buckets inside and issue doesn't have any relation with the Raw data bucket, KPI bucket, or data retention period. It's happening randomly for any bucket.

  • we had 5 Orgs one default one and the other orgs will be org_A, org_B, org_C, and org_D.
  • Each org has two buckets one with the Raw data and one with the KPI data which is calculated from the Raw data bucket.
  • Raw data buckets have data retention of 180 days and KPI data buckets have 730 days data retention.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/2.x OSS 2.0 related issues and PRs team/edge
Projects
None yet
Development

No branches or pull requests

2 participants