[
https://issues.apache.org/jira/browse/FLINK-25321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yang Wang closed FLINK-25321.
-----------------------------
Resolution: Information Provided
> standalone deploy on k8s,pod always OOM killed,actual heap memory usage is
> normal, gc is normal
> -----------------------------------------------------------------------------------------------
>
> Key: FLINK-25321
> URL: https://issues.apache.org/jira/browse/FLINK-25321
> Project: Flink
> Issue Type: Bug
> Components: Deployment / Kubernetes
> Affects Versions: 1.11.3
> Environment: Flink 1.11.3
> k8s v1.21.0
> standlone deployment
> Reporter: Gao Fei
> Priority: Major
>
> Start a cluster on k8s, deploy in standalone mode, a jobmanager pod (1G) and
> a taskmanager pod (3372MB limit), the total memory configuration of the Flink
> TM process is 3072MB, and the managed configuration is 0, both of which are
> on the heap memory. Now the pod It will always be OOM killed, and the total
> process memory will always exceed 3072MB. I saw that the system has adopted
> jemlloc. There is no 64M problem. The application itself has not applied for
> direct memory. It is strange why the process is always killed by OOM after a
> period of time.
>
> INFO [] - Final TaskExecutor Memory configuration:
> INFO [] - Total Process Memory: 3.000gb (3221225472 bytes)
> INFO [] - Total Flink Memory: 2.450gb (2630667464 bytes)
> INFO [] - Total JVM Heap Memory: 2.080gb (2233382986 bytes)
> INFO [] - Framework: 128.000mb (134217728 bytes)
> INFO [] - Task: 1.955gb (2099165258 bytes)
> INFO [] - Total Off-heap Memory: 378.880mb (397284478 bytes)
> INFO [] - Managed: 0 bytes
> INFO [] - Total JVM Direct Memory: 378.880mb (397284478 bytes)
> INFO [] - Framework: 128.000mb (134217728 bytes)
> INFO [] - Task: 0 bytes
> INFO [] - Network: 250.880mb (263066750 bytes)
> INFO [] - JVM Metaspace: 256.000mb (268435456 bytes)
> INFO [] - JVM Overhead: 307.200mb (322122552 bytes)
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
