[ 
https://issues.apache.org/jira/browse/FLINK-18152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17126688#comment-17126688
 ] 

Chesnay Schepler commented on FLINK-18152:
------------------------------------------

In a similar vein, if {{jobmanager.memory.process.size}} is set to low value 
you also get an exception, but the process starts nonetheless:
{code}
[] - The derived from fraction jvm overhead memory (512.000kb (524288 bytes)) 
is less than its min value 192.000mb (201326592 bytes), min value will be used 
instead                                                                         
Exception in thread "main" 
org.apache.flink.configuration.IllegalConfigurationException: Sum of configured 
JVM Metaspace (256.000mb (268435456 bytes)) and JVM Overhead (192.000mb 
(201326592 bytes)) exceed configured Total Process Memory$        at 
org.apache.flink.runtime.util.config.memory.ProcessMemoryUtils.deriveJvmMetaspaceAndOverheadWithTotalProcessMemory(ProcessMemoryUtils.java:133)
                                                                                
           at 
org.apache.flink.runtime.util.config.memory.ProcessMemoryUtils.deriveProcessSpecWithTotalProcessMemory(ProcessMemoryUtils.java:102)
                                                                                
                       at 
org.apache.flink.runtime.util.config.memory.ProcessMemoryUtils.memoryProcessSpecFromConfig(ProcessMemoryUtils.java:79)
                                                                                
                                    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}

Either there should also be a minimum total process memory to properly handle 
the JMV overhead minimum, or this should fail the startup.

> 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
>            Priority: Major
>
> 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)

Reply via email to