delete points throws 408 timeout
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.4k
- Forks
- 304
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 37
Description
When using qdrant-client 1.8.2 it’s throwing 408 timeout sometimes on the delete points endpoint, when starting to run it massively
it happens both using qdrant on docker or qdrant cloud.
the current solution was to switch to grpc and worked well, but would like to not need to switch to grpc for this
I already increase the timeout config, even tried to change on the lib with httpx but without success
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the intermittent 408s from qdrant-client 1.8.2 by running massive delete-points requests against Qdrant on Docker and Qdrant Cloud. Compare the HTTP endpoint with the working gRPC path, and inspect the timeout configuration and attempted httpx changes. Done means HTTP deletion completes reliably under the reported load without requiring gRPC.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100