[
https://issues.apache.org/jira/browse/FLINK-19461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17231575#comment-17231575
]
Kostas Kloudas commented on FLINK-19461:
----------------------------------------
I think that this has to do with how we split the total memory into the
different "partitions". When I run the command with memory equal to {{3g}} on a
local YARN cluster then everything goes smoothly and the correct value is
displayed.
I do not think that this is a bug but rather a misleading error message.
[~azagrebin] do you have an idea on how to improve it so that it displays sth
like "Not sufficient memory provided (X mb) ..." so that the user also sees
what he/she configured.
> yarn-sesson.sh -jm -tm arguments have no effect
> -----------------------------------------------
>
> Key: FLINK-19461
> URL: https://issues.apache.org/jira/browse/FLINK-19461
> Project: Flink
> Issue Type: Bug
> Components: Command Line Client, Deployment / YARN
> Affects Versions: 1.12.0
> Reporter: Robert Metzger
> Priority: Major
> Labels: usability
> Fix For: 1.12.0
>
> Attachments: jobmanager.log, yarn-debug.log
>
>
> It seems that I can set arbitrary values for the documented {{-jm}} and
> {{-tm}} arguments, not leading to any effects.
> Example: {{./bin/yarn-session -jm 512m -tm 512m}} should fail in my opinion,
> but it starts with the default memory configuration (1280mb / 1200mb? or so).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
