hiliuxg created FLINK-15415:
-------------------------------
Summary: Flink machine node memory is consumed quickly, but the
heap has not changed
Key: FLINK-15415
URL: https://issues.apache.org/jira/browse/FLINK-15415
Project: Flink
Issue Type: Bug
Components: Runtime / State Backends
Affects Versions: 1.8.0
Environment: machine : 256G memory , SSD , 32 CORE CPU
config :
jobmanager.heap.size: 4096m
taskmanager.heap.size: 144gb
taskmanager.numberOfTaskSlots: 48
taskmanager.memory.fraction: 0.7
taskmanager.memory.off-heap: false
parallelism.default: 1
Reporter: hiliuxg
The Flink node has been running for 1 month, and it is found that the machine's
memory is getting higher and higher, even exceeding the memory configured by
the heap. Through top -c, it is found that the machine's memory and virtual
memory are very high. It may be an off-heap memory leak. What is the collection
mechanism of flink's off-heap memory? It need to start FULL GC to recycle
off-heap memory?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
