[
https://issues.apache.org/jira/browse/FLINK-24120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17408594#comment-17408594
]
no nO edited comment on FLINK-24120 at 9/2/21, 6:51 AM:
--------------------------------------------------------
but my flink version is 1.13.2 ,and use image from docker pull
amd64/flink:1.13.2-scala_2.11-java11, I mean, this problem should be resolved
in 1.12? In the 1.12 official image, the memory allocator of jemalloc has been
used to solve this problem.
was (Author: 593700624):
but my flink version is 1.13.2 ,and use images from docker pull
amd64/flink:1.13.2-scala_2.11-java11
> The memory will rise a little after each savepoint ends
> -------------------------------------------------------
>
> Key: FLINK-24120
> URL: https://issues.apache.org/jira/browse/FLINK-24120
> Project: Flink
> Issue Type: Bug
> Components: flink-docker
> Affects Versions: 1.13.2
> Environment: flink on k8s
> flink version : 1.13.2
> state.backend: rocksdb
> state.checkpoints.dir: hdfs_url
> state.savepoints.dir: hdfs_url
> state.backend.rocksdb.memory.managed: true
>
> Reporter: no nO
> Priority: Blocker
> Attachments: image-2021-09-02-10-40-36-043.png, 截屏2021-09-02
> 上午10.44.10.png
>
>
> !image-2021-09-02-10-40-36-043.png!
> My task will do a savepoint every hour, so every hour will do a savepoint.
> From the memory monitoring, it can be seen that the memory of each hour will
> soar up, although the memory will drop a little later, but from every hour
> From the point of view of the memory peak on the whole point, the memory
> continues to rise little by little, and eventually rises to the limited
> memory, which will lead to being killed by k8S
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
