[
https://issues.apache.org/jira/browse/FLINK-18718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17165404#comment-17165404
]
Yang Wang commented on FLINK-18718:
-----------------------------------
[~flolas] Since the community decides to deprecate the cli options in the
future, see the discussion here[1], they are not supported in Yarn application
mode, Kubernetes session, Kubernetes application mode now.
[1].
https://issues.apache.org/jira/browse/FLINK-15179?focusedCommentId=16995321&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16995321
> Support for using yarn-cluster CLI parameters on application mode
> -----------------------------------------------------------------
>
> Key: FLINK-18718
> URL: https://issues.apache.org/jira/browse/FLINK-18718
> Project: Flink
> Issue Type: Improvement
> Components: Command Line Client
> Affects Versions: 1.11.0, 1.11.1
> Environment: *Flink 1.11*
> *CDH6.2.1*
> Reporter: Felipe Lolas
> Priority: Minor
>
> Hi!
> Just a minor improv. here:
> Now with the new Application Mode, we need to use generic cli configurations
> for setting up YARN deployments.
> *Example*
> {code:java}
> -Djobmanager.memory.process.size=1024m
> -Dtaskmanager.memory.process.size=1024m
> -Dyarn.application.queue=root.test
> -Dyarn.application.name=flink-hbase
> -Dyarn.application.type=flink {code}
> It would be nice to use directly the CLI options available for yarn-cluster.
> This works in run per-job and session mode *but not in application mode.*
>
> Thanks
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
