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 2020/06/08 09:00:05 UTC
[jira] [Assigned] (FLINK-18152) Master starts despite
IllegalConfigurationException
[ https://issues.apache.org/jira/browse/FLINK-18152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrey Zagrebin reassigned FLINK-18152:
---------------------------------------
Assignee: Andrey Zagrebin
> 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
>
> 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)