[
https://issues.apache.org/jira/browse/FLINK-11376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16745055#comment-16745055
]
Till Rohrmann commented on FLINK-11376:
---------------------------------------
Hi [~shengjk1], I don't fully understand the problem description. One comment,
though, {{-yn}} will only be respected by Flink's legacy mode. The legacy mode
has been removed with Flink 1.7. I would recommend not setting the parallelism
in code and in stead use the {{-p}} flag of Flink's CLI to specify the desired
parallelism.
> flink cli -yn -ys is not effect if (yn * ys)<parallelism ( this
> parallelism form env.setParallelism(parallelism) ) ;
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: FLINK-11376
> URL: https://issues.apache.org/jira/browse/FLINK-11376
> Project: Flink
> Issue Type: Bug
> Affects Versions: 1.7.1
> Environment: java: jdk1.8.0_151
> flink: flink-1.7.1
> CDH:CDH-5.13.1-1.cdh5.13.1.p0.2
> Reporter: shengjk1
> Priority: Major
> Attachments: Main222.java, image-2019-01-17-14-25-34-206.png
>
>
> Such as the title
> if (yn * ys)<parallelism ( this parallelism form
> env.setParallelism(parallelism) ) the yn and ys is not effect
> my application is flink streaming read kafka . this kafka topic has 3
> partition,and setParallelism(3) in code.when i use cli submiitjobs
> flink-1.7.1/bin/flink run -m yarn-cluster -yn 1 -ys 1 -ynm test
> -ccom.ishansong.bigdata.Main222 ./flinkDemo-1.0-SNAPSHOT.jar
> the application apply for 4 cpu cores and 4 containers from yarn web ui
> !image-2019-01-17-14-25-34-206.png!
> but if code is not write env.setParallelism(parallelism) or
> (yn*ys)>parallelism ,the yn、ys will effect. if code write
> env.setParallelism(parallelism) ，the final application resources are yn
> multiples and ys multiples. such as parallelism=10,yn=1 ys=5,the final
> application resources:cpu cores=11 containers=3
>
> Reproduce for the convenience of bugs，offer codes
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
