[FLINK-20171] Improve error message for Flink process memory configuration

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Done
• Affects Version/s: 1.11.0
• Fix Version/s: 1.11.0, 1.12.0
• Component/s: Runtime / Coordination
• Labels: pull-request-available usability
• Assignee: Andrey Zagrebin
• Reporter: Andrey Zagrebin
• Created: 16/Nov/20 14:15
• Updated: 17/Nov/20 14:12
• Resolved: 17/Nov/20 14:12

Description

Originates from discussion in FLINK-19461.

Currently, all configuration failures will result in IllegalConfigurationException from JobManagerProcessUtils and TaskExecutorProcessUtils. The exception error messages do not refer to the process type (JM or TM), it can only become clear from the stack trace.

We can wrap main configuration calls with extra try/catch (TaskExecutorProcessUtils::processSpecFromConfig and JobManagerProcessUtils::processSpecFromConfigWithNewOptionToInterpretLegacyHeap) where IllegalConfigurationException is wrapped into another one which states type of the process (JM or TM).

Issue Links

• relates to: FLINK-13980 FLIP-49 Unified Memory Configuration for TaskExecutors
• relates to: FLINK-16614 FLIP-116 Unified Memory Configuration for Job Manager
• links to: GitHub Pull Request #14083