[
https://issues.apache.org/jira/browse/FLINK-19461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17233927#comment-17233927
]
Robert Metzger commented on FLINK-19461:
----------------------------------------
I can confirm that everything works as expected. {{./bin/yarn-session.sh -jm
512m -tm 512m}} fail as expected, in FLink 1.11.1, 1.11.2 and 1.12.0-rc1.
I'm sorry for the time wasted by everybody who has looked into this issue so
far.
The problem was that I confused the "jm" and "ytm" arguments, with are for the
yarn session script, and regular CLI script.
I'm closing this ticket.
> 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)
