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
Issue with connecting to Elasticsearch #281
Comments
It is "normal" to see connection errors when using the docker-compose file like that. Due to the slow startup of the elasticsearch container, and the really fast startup of py-image-dedup, the latter tries to connect to the db before it is up and running. To work around this py-image-dedup has a retry machanism, so waiting a couple of seconds usually lets the processing continue as normal. The real fix would be to have the elasticsearch instance running before launching the py-image-dedup container, or setup some kind of dependency between the two inside of the Since you do get logs about the "analyze" phase, I guess the order of the log output is just mixed up? |
This is exactly what my docker-compose addition does: healthcheck:
test: ["CMD", "curl", "-f", "http://localhost:9200"]
interval: 30s
timeout: 30s
retries: 10 depends_on:
elasticsearch:
condition: service_healthy My issue is that after the initial phase elasticsearch becomes unresponsive:
|
I cannot reproduce this. I don't use the docker-compose file in production, I use individual containers managed within a kubernetes cluster. Do you get the same behavior with the docker-compose file in this repo? |
Thanks for getting back to me! I'm currently running
But after some time i get the same issue as before:
It is definitely an Elasticsearch issue:
I'll investigate some more. |
I will close this issue due to inactivity. Feel free to reopen if needed. |
Describe the bug
I'm having issue with connections to my Elasticsearch instance.
The following is an example of the behaviour I'm experiences. I'm not sure how to handle it or if it is an issue with Elasticsearch or
py-image-dedup
.issue
To Reproduce
Running with the following
The text was updated successfully, but these errors were encountered: