You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Andrey Zagrebin (Jira)" <ji...@apache.org> on 2019/12/17 13:49:00 UTC
[jira] [Assigned] (FLINK-15288) Starting jobmanager pod should
respect containerized.heap-cutoff
[ https://issues.apache.org/jira/browse/FLINK-15288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrey Zagrebin reassigned FLINK-15288:
---------------------------------------
Assignee: Yang Wang
> Starting jobmanager pod should respect containerized.heap-cutoff
> ----------------------------------------------------------------
>
> Key: FLINK-15288
> URL: https://issues.apache.org/jira/browse/FLINK-15288
> Project: Flink
> Issue Type: Sub-task
> Reporter: Yang Wang
> Assignee: Yang Wang
> Priority: Blocker
> Fix For: 1.10.0
>
>
> Starting jobmanager pod should respect containerized.heap-cutoff. The cutoff will be used to leave some memory for jvm off-heap, for example meta space, thread native memory and etc.
>
> {code:java}
> public static final ConfigOption<Float> CONTAINERIZED_HEAP_CUTOFF_RATIO = ConfigOptions
> .key("containerized.heap-cutoff-ratio")
> .defaultValue(0.25f)
> .withDeprecatedKeys("yarn.heap-cutoff-ratio")
> .withDescription("Percentage of heap space to remove from containers (YARN / Mesos / Kubernetes), to compensate" +
> " for other JVM memory usage.");
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)