Skip to content

Import of large json fails #365

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

Open
PietrH opened this issue Mar 11, 2025 · 4 comments
Open

Import of large json fails #365

PietrH opened this issue Mar 11, 2025 · 4 comments
Milestone

Comments

@PietrH
Copy link
Member

PietrH commented Mar 11, 2025

I'm getting a 504 Gateway Timeout when trying to import a large JSON (4MB).

I've had this issue before, and some imports might actually have gone trough even though I got the 504. This is leading to duplicate records in UAT, which we want to avoid for production.

2025_03_06-16_22-vespadb_import_iasset.json

@PietrH
Copy link
Member Author

PietrH commented Mar 11, 2025

If there is something wrong with the import file, an error would be preferred over the Gateway error.

@PietrH PietrH added this to the v1.x milestone Mar 25, 2025
@PietrH
Copy link
Member Author

PietrH commented Mar 31, 2025

504 gateway timeout on

2025_03_31-13_40-vespadb_import_iasset.json

@PietrH
Copy link
Member Author

PietrH commented May 7, 2025

504 Gateway Time-out on

2025_05_07-13_59-vespadb_import_iasset.json

@PietrH
Copy link
Member Author

PietrH commented May 7, 2025

504 Gateway Time-out on

2025_05_07-13_59-vespadb_import_iasset.json

@stevegerrits I got a timetout, but then 20 minutes later I noticed around 8000 extra records on UAT. So I believe (at least part of) the import was successful, but I got no messaging and have no way of knowing if all my records made it.

Any way we can avoid the timeouts? Is this a server resources thing?

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