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

Migration from AWS cloud to Azure cloud subscription fails with data loss #25270

Open
celinaT opened this issue Aug 26, 2024 · 1 comment
Open

Comments

@celinaT
Copy link

celinaT commented Aug 26, 2024

Steps to reproduce:

  1. Follow the migration guide as per the official documentation.
  2. Compare the size of the tables in the source and target databases after migration.
  3. Observe the data loss (30-40% missing).

Expected behaviour:

I have been following the official migration guide for InfluxDB v2 as outlined (https://docs.influxdata.com/influxdb/v2/write-data/migrate-data/migrate-cloud-to-oss/). I attempted the migration twice, using both methods provided in the documentation.

Although I did not encounter any migration errors during the process, I observed that the data was not fully migrated. Specifically, when comparing the table sizes between the source and target databases, I found that 30-40% of the data was missing in the target. There were no duplicates present in the source table, so that does not explain the discrepancy.

Actual behaviour:

Huge data losses in both cases, no errors in the logs

Environment info:

  • Source bucket in the AWS cloud
  • Destination bucket in the Azure cloud

Config:

  • start: 2023-12-01T00:00:00Z,
  • stop: 2024-08-31T00:00:00Z,
  • batchInterval: 1h,
  • option task = {
    name: "Migration",
    every: 30s,
    }
@celinaT
Copy link
Author

celinaT commented Aug 29, 2024

Any updates here?

@celinaT celinaT closed this as completed Aug 29, 2024
@celinaT celinaT reopened this Aug 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant