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

502 status code after some time #4299

Closed
Jasperav opened this issue Jan 4, 2024 · 2 comments
Closed

502 status code after some time #4299

Jasperav opened this issue Jan 4, 2024 · 2 comments
Labels
needs more info This issue needs a minimal complete and verifiable example

Comments

@Jasperav
Copy link

Jasperav commented Jan 4, 2024

Describe the bug
I am running Meilisearch 1.5.0 on AWS on t3.medium and 100 gb storage for testing purposes. I have a setup script which I run to add 250.000 documents. After 1 hour, around 80.000 documents are successfully added. However, for some reason, I suddenly get a 502 error response back from Meilisearch. How is this possible?

This is the raw response:

MeilisearchCommunication(\n MeilisearchCommunicationError {\n status_code: 502,\n message: None,\n url: \"http://34.xxx.xxx.16/tasks/78165\",\n },\n)
I get this while waiting for a task to be completed with this method call (Rust client):

wait_for_completion_successful

After calling add_or_replace.

@curquiza
Copy link
Member

curquiza commented Jan 4, 2024

Hello @Jasperav

Do you have a similar issue with using curl and not the Rust client?
Also, this error means it's impossible to reach the server, it's not from Meilisearch, but from the server and returned by the Rust client -> are you sure the server was up all the time?

@curquiza curquiza added the needs more info This issue needs a minimal complete and verifiable example label Jan 4, 2024
@Jasperav
Copy link
Author

Jasperav commented Jan 4, 2024

Thanks for the quick response, the batch import is successfully now without any issues, guess I had some sort of network issue after all.

@Jasperav Jasperav closed this as completed Jan 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs more info This issue needs a minimal complete and verifiable example
Projects
None yet
Development

No branches or pull requests

2 participants