delete points throws 408 timeout
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
Tracestack
File "/Users/emanuel/Library/Caches/pypoetry/virtualenvs/experiemental/lib/python3.11/site-packages/qdrant_client/async_qdrant_remote.py", line 1431, in delete
await self.openapi_client.points_api.delete_points(
File "/Users/emanuel/Library/Caches/pypoetry/virtualenvs/experiemental/lib/python3.11/site-packages/qdrant_client/http/api/points_api.py", line 824, in delete_points
return await self._build_for_delete_points(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/emanuel/Library/Caches/pypoetry/virtualenvs/experiemental/lib/python3.11/site-packages/qdrant_client/http/api_client.py", line 148, in request
return await self.send(request, type_)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/emanuel/Library/Caches/pypoetry/virtualenvs/experiemental/lib/python3.11/site-packages/qdrant_client/http/api_client.py", line 171, in send
raise UnexpectedResponse.for_response(response)
qdrant_client.http.exceptions.UnexpectedResponse: Unexpected Response: 408 (Request Timeout)
Raw response content:
b''
Hey @EmanuelCampos
We will need some additional info to look into it
- What does your collection info look like? (https://qdrant.tech/documentation/concepts/collections/?q=collection#collection-info)
- How do you upsert code? (code snippet)
- Do you have payload and do you use payload filters? (an example of your payload, it might be obfuscated, we mostly care about types)
- How do you search? (code snippet)
@joein You are having the exact same problem, here are information about the collections
Collection AO_Metro_2024_Sud_Ouest
{ "result": { "status": "green", "optimizer_status": "ok", "indexed_vectors_count": 0, "points_count": 219, "segments_count": 2, "config": { "params": { "vectors": { "size": 1024, "distance": "Cosine" }, "shard_number": 1, "replication_factor": 1, "write_consistency_factor": 1, "on_disk_payload": true }, "hnsw_config": { "m": 16, "ef_construct": 100, "full_scan_threshold": 10000, "max_indexing_threads": 0, "on_disk": false }, "optimizer_config": { "deleted_threshold": 0.2, "vacuum_min_vector_number": 1000, "default_segment_number": 0, "max_segment_size": null, "memmap_threshold": null, "indexing_threshold": 20000, "flush_interval_sec": 5, "max_optimization_threads": null }, "wal_config": { "wal_capacity_mb": 32, "wal_segments_ahead": 0 }, "quantization_config": null }, "payload_schema": {} }, "status": "ok", "time": 0.000034053 }
We are facing HTTP.408 errors when creating and searching the collection or requesting the existing collections Here is a code snippet
from qdrant_client import QdrantClient client = QdrantClient(url="http://10.80.34.17:6333") client.get_collections()
Expected result :
{ "result": { "collections": [ { "name": "mistral_test" }, { "name": "mixtral" }, { "name": "TLE_timeout" }, { "name": "AO_Metro_2024_Sud_Ouest" }, { "name": "mixtral_test" }, { "name": "my_collection" } ] }, "status": "ok", "time": 0.000005537 }