[
https://issues.apache.org/jira/browse/FLINK-20171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Zagrebin closed FLINK-20171.
-----------------------------------
Resolution: Done
merged into master by 2ad92169a4a4ffc92d32783f8777a132e1dac7c4
merged into 1.11 by 5a8cc80ce20cdc933bf78d9858d22d3b80dc8f98
> Improve error message for Flink process memory configuration
> ------------------------------------------------------------
>
> Key: FLINK-20171
> URL: https://issues.apache.org/jira/browse/FLINK-20171
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Coordination
> Affects Versions: 1.11.0
> Reporter: Andrey Zagrebin
> Assignee: Andrey Zagrebin
> Priority: Major
> Labels: pull-request-available, usability
> Fix For: 1.12.0, 1.11.0
>
>
> 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).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
