[
https://issues.apache.org/jira/browse/FLINK-18152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Zagrebin closed FLINK-18152.
-----------------------------------
Resolution: Fixed
merged into master by 44acd5017502688be128e7208dcd2f1fbfc7c396
merged into 1.11 by 822e8a3b67bcf48551eaaa124d987c684c5008d3
> Master starts despite IllegalConfigurationException
> ---------------------------------------------------
>
> Key: FLINK-18152
> URL: https://issues.apache.org/jira/browse/FLINK-18152
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Coordination
> Affects Versions: 1.11.0
> Reporter: Chesnay Schepler
> Assignee: Andrey Zagrebin
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.11.0
>
>
> When no memory configuration parameters are set for the Master process then
> this exception is logged by the BashJavaUtils:
> {code}
> Exception in thread "main"
> org.apache.flink.configuration.IllegalConfigurationException: Either required
> fine-grained memory (jobmanager.memory.heap.size), or Total Flink Memory size
> (Key: 'jobmanager.memory.flink.size' , default: null $ at
> org.apache.flink.runtime.util.config.memory.ProcessMemoryUtils.failBecauseRequiredOptionsNotConfigured(ProcessMemoryUtils.java:111)
>
> at
> org.apache.flink.runtime.util.config.memory.ProcessMemoryUtils.memoryProcessSpecFromConfig(ProcessMemoryUtils.java:81)
>
> at
> org.apache.flink.runtime.jobmanager.JobManagerProcessUtils.processSpecFromConfig(JobManagerProcessUtils.java:76)
>
> at
> org.apache.flink.runtime.jobmanager.JobManagerProcessUtils.processSpecFromConfigWithNewOptionToInterpretLegacyHeap(JobManagerProcessUtils.java:71)
>
> at
> org.apache.flink.runtime.util.bash.BashJavaUtils.getJmResourceParams(BashJavaUtils.java:92)
>
> at
> org.apache.flink.runtime.util.bash.BashJavaUtils.runCommand(BashJavaUtils.java:66)
>
> at
> org.apache.flink.runtime.util.bash.BashJavaUtils.main(BashJavaUtils.java:54)
> {code}
> Afterwards, the Master process however continues to start just fine.
> TaskManagers will not be started given the same situation, which is
> inconsistent behavior, and it seems dangerous to start a process despite an
> illegal configuration.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
