You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Zhu Zhu (Jira)" <ji...@apache.org> on 2020/08/10 07:34:00 UTC
[jira] [Closed] (FLINK-14836) Unable to set yarn container number
for scala shell in yarn mode
[ https://issues.apache.org/jira/browse/FLINK-14836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zhu Zhu closed FLINK-14836.
---------------------------
Resolution: Won't Fix
Closing this JIRA because setting container number in yarn mode does not work long ago (since FLIP-6). And FLINK-14838 further cleaned up the legacy documentation for it.
Need to mention that an improvement FLINK-15959 is on the way to launch containers in ahead like `-n` once does.
> Unable to set yarn container number for scala shell in yarn mode
> ----------------------------------------------------------------
>
> Key: FLINK-14836
> URL: https://issues.apache.org/jira/browse/FLINK-14836
> Project: Flink
> Issue Type: Bug
> Components: Scala Shell
> Affects Versions: 1.10.0
> Reporter: Jeff Zhang
> Priority: Major
> Fix For: 1.10.2, 1.12.0
>
>
> In FLINK-12362, "-n" is removed which cause unable to set container number for scala shell in yarn mode. The root cause is that start-scala-shell didn't use `flink run` which means it doesn't support all the parameters of flink run (including -p).
> Either we need to revert FLINK-12362, or make start-scala-shell use `flink run`
--
This message was sent by Atlassian Jira
(v8.3.4#803005)