[ https://issues.apache.org/jira/browse/FLINK-30081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Flink Jira Bot updated FLINK-30081: ----------------------------------- Labels: pull-request-available stale-major (was: pull-request-available) I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community manage its development. I see this issues has been marked as Major but is unassigned and neither itself nor its Sub-Tasks have been updated for 60 days. I have gone ahead and added a "stale-major" to the issue". If this ticket is a Major, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized. > Local executor can not accept different jvm-overhead.min/max values > ------------------------------------------------------------------- > > Key: FLINK-30081 > URL: https://issues.apache.org/jira/browse/FLINK-30081 > Project: Flink > Issue Type: Improvement > Components: Runtime / Configuration > Affects Versions: 1.16.0 > Reporter: Mingliang Liu > Priority: Major > Labels: pull-request-available, stale-major > > In local executor, it's not possible to set different values for > {{taskmanager.memory.jvm-overhead.max}} and > {{{}taskmanager.memory.jvm-overhead.min{}}}. The same problem for > {{taskmanager.memory.network.max}} and {{{}taskmanager.memory.network.min{}}}. > Sample code to reproduce: > {code:java} > Configuration conf = new Configuration(); > conf.setString(TaskManagerOptions.JVM_OVERHEAD_MIN.key(), "1GB"); > conf.setString(TaskManagerOptions.JVM_OVERHEAD_MAX.key(), "2GB"); > StreamExecutionEnvironment.createLocalEnvironment(conf) > .fromElements("Hello", "World") > .executeAndCollect() > .forEachRemaining(System.out::println); {code} > The failing exception is something like: > {code:java} > Exception in thread "main" java.lang.IllegalArgumentException > at org.apache.flink.util.Preconditions.checkArgument(Preconditions.java:122) > at > org.apache.flink.runtime.taskexecutor.TaskExecutorResourceUtils.calculateTotalProcessMemoryFromComponents(TaskExecutorResourceUtils.java:182) > at > org.apache.flink.runtime.taskexecutor.TaskExecutorMemoryConfiguration.create(TaskExecutorMemoryConfiguration.java:119) > {code} > I think the problem was that we expect the max and min to equal, but local > executor did not reset them correctly? -- This message was sent by Atlassian Jira (v8.20.10#820010)