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

MeiliSearch::CommunicationError: An error occurred while trying to connect to the MeiliSearch instance #365

Open
drale2k opened this issue Jun 19, 2024 · 3 comments

Comments

@drale2k
Copy link

drale2k commented Jun 19, 2024

Description
I started to get the following error regularly when performing a search

MeiliSearch::CommunicationError: An error occurred while trying to connect to the MeiliSearch instance: failed to connect: getaddrinfo: nodename nor servname provided, or not known

The code is a simple search request:

Episode.search(formatted_keyword, filter: [ "transcribed_at > #{start_from_date.to_i}" ])

This code is running in a background job every 10 minutes, through a cron job setup with good_job. When it happens, which is irregular, it seems to happen a couple of times before it stops throwing an error and starts working again.

It definitely seems to be related to the timeout issue reported previously #355 as it also throws the same error before causing the error above. See the attached screenshot

Screenshot 2024-06-19 at 18 54 59

The Episode index is very small, about 150 entries with relatively little data.

Screenshots or Logs
If applicable, add screenshots or logs to help explain your problem.

Environment (please complete the following information):

@ellnix
Copy link
Collaborator

ellnix commented Jul 23, 2024

It looks like it might be a problem with the connection logic, probably specific to background jobs. It looks like you can stop using that httprb branch and switch to main. I'll see if I can reproduce it.

@drale2k
Copy link
Author

drale2k commented Jul 23, 2024

I am using the httprb branch mainly because of #355

Is it no longer needed for the other issue as well?

@ellnix
Copy link
Collaborator

ellnix commented Jul 23, 2024

I am using the httprb branch mainly because of #355

Is it no longer needed for the other issue as well?

It looks like the httprb change failed to fix it, so now I'm thinking it might be related to this issue.

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

2 participants