[
https://issues.apache.org/jira/browse/FLINK-15288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16998233#comment-16998233
]
Andrey Zagrebin commented on FLINK-15288:
-----------------------------------------
We also need to fix this option description that it is only for job master now
after FLIP-49.
Have you encountered a problem with the new kubernetes deployment because this
option support is missing or is it just to align with Yarn integration atm?
If there is no real problem we can change the priority to major for this issue
and add this option support later if it cannot make it into 1.10.
because it potentially affects only specific deployments and we are going to
move job master memory configuration to new FLIP-49 way soon as we have done
for task executor.
> 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
> 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)
