[
https://issues.apache.org/jira/browse/FLINK-35192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17842322#comment-17842322
]
Biao Geng commented on FLINK-35192:
-----------------------------------
[~stupid_pig], it looks like that pictures of the pmap is broken. But the glibc
issue is well known, if that's the case, it makes sense to me to introduce
jemalloc.
> operator oom
> ------------
>
> Key: FLINK-35192
> URL: https://issues.apache.org/jira/browse/FLINK-35192
> Project: Flink
> Issue Type: Bug
> Components: Kubernetes Operator
> Affects Versions: kubernetes-operator-1.6.1
> Environment: jdk: openjdk11
> operator version: 1.6.1
> Reporter: chenyuzhi
> Priority: Major
> Labels: pull-request-available
> Attachments: image-2024-04-22-15-47-49-455.png,
> image-2024-04-22-15-52-51-600.png, image-2024-04-22-15-58-23-269.png,
> image-2024-04-22-15-58-42-850.png, image-2024-04-30-16-47-07-289.png,
> image-2024-04-30-17-11-24-974.png, screenshot-1.png, screenshot-2.png,
> screenshot-3.png
>
>
> The kubernetest operator docker process was killed by kernel cause out of
> memory(the time is 2024.04.03: 18:16)
> !image-2024-04-22-15-47-49-455.png!
> Metrics:
> the pod memory (RSS) is increasing slowly in the past 7 days:
> !screenshot-1.png!
> However the jvm memory metrics of operator not shown obvious anomaly：
> !image-2024-04-22-15-58-23-269.png!
> !image-2024-04-22-15-58-42-850.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
