weaviate_go_memstats_heap_allocated_size

The number of heap bytes allocated and still in use in the Weaviate instance

Dimensions:None

Technical Annotations (22)

Configuration Parameters (5)

GOMEMLIMITrecommended: 10-20% of total memory (e.g., 10GiB for 100GiB nodes)

Controls Go garbage collector soft memory limit; 50GiB on 100GiB nodes (50%) is too high

vectorCacheMaxObjectsrecommended: 500000000000

Half the default value to reduce memory pressure

cpuPercentagerecommended: not specified

Backup parameter to limit CPU usage during backup operations

GOGCrecommended: 20

More aggressive garbage collection to prevent memory accumulation

ASYNC_REPLICATION_HASHTREE_HEIGHTrecommended: reduce for many tenants, increase for very large collections

Controls memory footprint vs efficiency of diff identification

Error Signatures (4)

cannot reach enough replicaslog pattern

cannot achieve consistency level "QUORUM": read errorlog pattern

WeaviateTimeoutError: The request to Weaviate timed out while awaiting a responseexception

httpx.RemoteProtocolError: Server disconnected without sending a responseexception

CLI Commands (1)

client.collections.delete_all()diagnostic

Technical References (12)

S3 backupcomponentBACKUP_S3_BUCKETconfigurationGo garbage collectorcomponentHNSW indexcomponentcollectioncomponentschema structureconceptvectorsconcepthash treecomponenttenantconceptmulti-tenant collectionconceptminio-gocomponentmulti-part uploadprotocol

Related Insights (11)

OOM kill causes persistent collection metadata desynchronizationcritical

▸

Memory increases during S3 backup and never returns to baselinecritical

▸

GOMEMLIMIT set above recommended threshold causes suboptimal GC behaviorwarning

▸

Memory formula underprovisioning causes cluster failure with multi-tenancy and updatescritical

▸

HNSW index rebuilding doubles memory causing OOM crashescritical

▸

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

▸

Memory usage more than doubles after upgrading Weaviate 1.18 to 1.25warning

▸

Memory consumption grows as document count increaseswarning

▸

Collection deletion operations timeout despite successful executionwarning

▸

High memory footprint in multi-tenant deploymentswarning

▸

Unconfigured MinIO part size causes memory bloat during backupswarning

▸