qdrant-client
qdrant-client copied to clipboard
Significance of first grpc calls failing with StatusCode.UNAVAILABLE
Hi,
i am trying to use a dockerized qdrant server, feeding information into it from another container running the qdrant-client over grpc.
I noticed that I almost always the FIRST grpc call fails with StatusCode.UNAVAILABLE "DNS resolution failed for "qdrant":6334: C-ares status is not ARES_SUCCESS qtype=A name="qdrant" is_balancer=0: Domain name not found"
Doing a repeat of the same call after a little pause succeeds. I have no clue if this has to qdrant of with docker, but did anyone encounter a similar behaviour?
Hi
Could it be that your Qdrant instance didn't have enough time to initialize?
If you use docker-compose it might be useful to set depends_on
or just add some timeout before the first call
I actually had added some sleep statement (its painful to admin) to the entrypoint of the service relying on qdrant. None the less, I can see the same behavior.
Could you please provide more information about your environment / code snippets / instructions how to reproduce the issue?