Technologies/DataHub/jvm_memory_used
DataHubDataHubMetric

jvm_memory_used

Amount of JVM memory currently used
Dimensions:None
Available on:Native (1)PrometheusPrometheus (1)
Interface Metrics (2)
Native
Amount of JVM memory currently used
Dimensions:None
PrometheusPrometheus
Amount of JVM memory used
Dimensions:None
Sources
jvm_memory_useddatahubproject.io
Related Insights (3)
Elasticsearch Memory Pressure from Unindexed Schema Fieldscritical

DataHub's search performance degrades when Elasticsearch cluster memory is exhausted by unoptimized index mappings or excessive schema fields. High heap usage combined with slow search queries indicates index buffer or field data cache exhaustion.

▸
JVM GC Pause Cascading to Kafka Consumer Lagwarning

Prolonged JVM garbage collection pauses in DataHub consumers cause Kafka consumer lag to spike. This creates a cascading failure where metadata ingestion stalls, leading to stale catalog data and failed data quality checks.

▸
JVM Memory Pressure GC Thrashingcritical

DataHub GMS or Frontend experiencing memory pressure causing frequent garbage collection pauses, degrading API response times and potentially leading to OutOfMemoryErrors and service unavailability.

▸