-
Notifications
You must be signed in to change notification settings - Fork 51
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
Consensus operation timeout issue #100
Comments
Status update: tested the following version combinations:
and still not working. |
Adding a few more logs in case they'd be helpful:
|
I'm running into what I believe is the same issue, with the difference that we're not actively scaling our Qdrant deployment -- it's just happening sporadically during usage. Will investigate whether there was some concurrent auto-scaling going on. |
We faced the same issue and fixed the same by increasing the min replica count to 3 in the HPA |
I'm running Qdrant vector database engine in Google Kubernetes and it was deployed by official Helm chart with minor modifications in values.yaml. It was running 3 replicas and I decided to increase it to 5. I ran Helm upgrade and it created 2 more replicas and they're all in Running state. When I run a search on existing collections, I get results immediately. However, I can't run create a new collection by using
client.recreate_collection
method.My Python client version: 1.0.5
Qdrant docker version version: 1.2.0
Here are my Python logs:
Kubernetes logs:
How can I fix this issue?
The text was updated successfully, but these errors were encountered: