Socket error using Windows and REST
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.4k
- Forks
- 301
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 37
Description
The following code:
from qdrant_client import QdrantClient
client = QdrantClient('http://localhost:6333')
collection_name = 'test'
offset = 0
while offset is not None:
response, offset_id = client.scroll(collection_name=collection_name, offset=offset, limit=1000)
offset = offset_id
for r in response:
r.payload['random'] = random # Put here whatever values you want
client.set_payload(
collection_name=collection_name,
payload=r.payload,
points=[r.id]
)
Gives an error in Windows if the collection has a lot of points (~40.000 in this test) with sockets:
OSError: [WinError 10048] Only one usage of each socket address (protocol/networ address/port) is normally permitted
With grpc it works fine
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 with the QdrantClient REST path exercised by scroll and set_payload, reproducing the example on Windows against a large collection. Compare its socket behavior with the working gRPC path. Done means repeatedly scrolling and updating roughly 40,000 points no longer raises WinError 10048.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100