[FLINK-18152] Master starts despite IllegalConfigurationException

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.11.0
• Fix Version/s: 1.11.0
• Component/s: Runtime / Coordination
• Labels: pull-request-available
• Assignee: Andrey Zagrebin
• Reporter: Chesnay Schepler
• Created: 05/Jun/20 11:17
• Updated: 09/Jun/20 16:44
• Resolved: 09/Jun/20 09:15

Description

When no memory configuration parameters are set for the Master process then this exception is logged by the BashJavaUtils:

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)

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.

Issue Links

• is a child of: FLINK-17973 Test memory configuration of Flink cluster
• relates to: FLINK-18217 config.sh#extractExecutionResults does not fail on wrong input
• links to: GitHub Pull Request #12521