You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Kostas Kloudas (Jira)" <ji...@apache.org> on 2020/10/07 14:04:00 UTC

[jira] [Commented] (FLINK-19461) yarn-sesson.sh -jm -tm arguments have no effect

    [ https://issues.apache.org/jira/browse/FLINK-19461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17209561#comment-17209561 ] 

Kostas Kloudas commented on FLINK-19461:
----------------------------------------

Thanks for looking into it! I have two clarifying questions:
1) what happens if you use {{yjm}} and {{ytm}}
2) (most important) can you enable debug logs or see if at the web ui if the {{jobmanager.memory.process.size}} is set correctly? This is important to see if it is the client that does not forward the option correctly (this should happen [here|https://github.com/apache/flink/blob/master/flink-yarn/src/main/java/org/apache/flink/yarn/cli/FlinkYarnSessionCli.java#L335] which seems to be called properly), or the cluster side does not interpret the option correctly.

> 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
>
>
> 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)