weaviate_queries_durations_ms

The number of operations observed in the query duration histogram by `upper_bound` buckets

Dimensions:None

Technical Annotations (22)

Configuration Parameters (4)

GOGC

Go GC tuning parameter to reduce pause frequency

timeout.initrecommended: 60

Initialization timeout in seconds for Weaviate Python client connection

timeout.queryrecommended: 240

Query timeout in seconds to prevent DEADLINE_EXCEEDED on large collections

timeout.insertrecommended: 240

Insert operation timeout in seconds for Weaviate Python client

Error Signatures (5)

entrypoint was deleted in the object store, it has been flagged for cleanup and should be fixed in the next cleanup cycle

log pattern

explorer: get class: vector search: object vector search at indexlog pattern

StatusCode.DEADLINE_EXCEEDEDerror code

Deadline Exceededlog pattern

cURL error 28: Operation timed out after 30001 milliseconds with 0 bytes receivederror code

Technical References (13)

entrypointcomponentshardcomponentobject storecomponentHNSWcomponentxlm Robertacomponentcustom vectorizercomponentHNSW indexcomponentGRPCprotocolhybrid searchconcepttombstonesconceptweaviate-python-clientcomponentweaviate-go-clientcomponentPython requests librarycomponent

Related Insights (9)

Vector search entrypoint deleted after backup restore cyclecritical

▸

Query latency degrades to 5-15s with 18M objects under default configurationwarning

▸

Garbage collection pauses cause query timeoutswarning

▸

Production query latency 10-50ms vs sub-millisecond benchmarksinfo

▸

Critical monitoring thresholds: 80% memory, 100ms latency, slow index rebuildsinfo

▸

Vector search latency degrades significantly at million-document scalewarning

▸

GRPC deadline exceeded on hybrid search queries for large collectionswarning

▸

Delete operation spikes cause query timeouts and latency degradationcritical

▸

Python client shows intermittent latency spikes for vector querieswarning

▸