Exponential backoff while uploading collection
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.4k
- Forks
- 304
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 37
Description
The upload_collection method allows setting the max_retries parameter, but in case of any issues, it just starts another attempt immediately. If a heavy process is running on the Qdrant server, we're sending some unnecessary requests it won't handle either way. I'd suggest implementing an exponential backoff so we do not fire consecutive requests but wait so the server can finish its work. From the user's perspective, nothing changes.
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
Start at the Python client's upload_collection method and trace how max_retries triggers repeated requests. Implement exponential delays between retry attempts without changing the method's user-facing behavior, then verify that retries no longer happen immediately and that successful uploads still complete normally.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- database
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100