datafusion.memory_pool.limit
Maximum memory limitDimensions:None
Technical Annotations (32)
Configuration Parameters (6)
RuntimeConfig.memory_poolrecommended: FairSpillPool with 2-3x expected memoryMemoryConsumer.with_can_spillrecommended: truedatafusion.optimizer.prefer_hash_joinrecommended: falsedatafusion.memory_pool.limitprefer_hash_joinhash_join_single_partition_thresholdError Signatures (3)
ResourcesExhausted("Additional allocation failedexceptionFailed to allocate additionallog patternResourcesExhaustedexceptionTechnical References (23)
memory_reservation_bytescomponentRepartitionExeccomponentExternalSortercomponentFairSpillPoolcomponenttry_growcomponentPrometheuscomponentDataDogcomponentGrafanacomponentHashAggregationExeccomponentGroupedHashAggregateStreamcomponentsort_batchcomponentBatchSplittercomponentmemory reservationsconceptHashJoincomponentSortMergeJoincomponentmemory poolcomponentmemory_poolcomponentspillingconceptunnestcomponentGROUP BYcomponentarray_aggcomponentstreaming executionconceptmemory spillingconceptRelated Insights (9)
Memory pool lacks dual watermark causing premature OOM errorswarning
▸
ExternalSort fails when non-spillable input operators exhaust memory poolcritical
▸
Resource exhaustion undetected without metric trackingwarning
▸
Hash aggregation spill doubles memory usage due to sort_batch copycritical
▸
BatchSplitter does not prevent memory issues from oversized join batchescritical
▸
Hash join fails when memory limit exceeded without spilling supportcritical
▸
Memory exhaustion from insufficient memory pool limits on resource-constrained systemscritical
▸
Unnest with GROUP BY causes unbounded memory growth despite streamingcritical
▸
Memory pressure during joins triggers disk spilling with performance impactwarning
▸