[
https://issues.apache.org/jira/browse/FLINK-15058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16988794#comment-16988794
]
Xintong Song commented on FLINK-15058:
--------------------------------------
I also don't like the idea about checking free heap size. We actually now
decide the memory sizes before launching the TM process (on RM side, or in
shell scripts by calling to the java codes), which means we do not know the
free memory size at all.
I think for containered scenarios this should't be a problem. People need to
set the container size anyway, and that's the same value for total process
memory. The question is do we want to force standalone users, who may have a
custom flink-conf.yaml that does not contain tm memory, to configure task
executor memory?
> Log required config keys if TaskManager memory configuration is invalid
> -----------------------------------------------------------------------
>
> Key: FLINK-15058
> URL: https://issues.apache.org/jira/browse/FLINK-15058
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Coordination
> Affects Versions: 1.10.0
> Reporter: Gary Yao
> Assignee: Gary Yao
> Priority: Major
> Fix For: 1.10.0
>
>
> Currently the error message is
> {noformat}
> Either Task Heap Memory size and Managed Memory size, or Total Flink Memory
> size, or Total Process Memory size need to be configured explicitly
> {noformat}
> However, it would be good to immediately see which config keys are expected
> to be configured.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
