[ https://issues.apache.org/jira/browse/FLINK-14836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16976349#comment-16976349 ]
vinoyang edited comment on FLINK-14836 at 11/18/19 8:23 AM: ------------------------------------------------------------ IMO, we can not revert FLINK-12362, because "-n" has not been supported before FLINK-12362, it just kept the config option. FLINK-12362 only removed the relevant config option. We should change the JIRA title because the container number is calculated which is the current implementation and can not be changed. I just found I did not do the full cleanup in FLINK-12362. There are some remaining docs of scala shell and python need to be removed about "-n". Will do it later, the JIRA issue is FLINK-14838. was (Author: yanghua): IMO, we can not revert FLINK-12362, because "-n" has not been supported before FLINK-12362, it just kept the config option. FLINK-12362 only removed the relevant config option. We should change the JIRA title because the container number is calculated which is the current implementation and can not be changed. I just found I did not do the full cleanup in FLINK-12362. There are some remaining docs of scala shell and python need to be removed about "-n". Will do it later. > 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 > Affects Versions: 1.10.0 > Reporter: Jeff Zhang > Priority: Major > > 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)