[
https://issues.apache.org/jira/browse/FLINK-12362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16829029#comment-16829029
]
Tony Xintong Song commented on FLINK-12362:
-------------------------------------------
Hi, [~yanghua],
I don't understand what is your concern about calculating the number of
containers in job cluster mode.
To my understanding, Flink launches TEs as many as the job needs by starting a
new TE whenever a slot request cannot be fulfilled. Users do not need to set
the number of TEs, which looks good to me.
There is a config option taskmanager.numberOfTaskSlots that controls the number
of slots per task executor. And if both the number of total tasks (depends on
parallelisms and operator chaining) and the number of slots per TE are
determined, then the number of TEs should also be determined.
> Recover container number config option for Flink on yarn job cluster mode in
> the doc
> ------------------------------------------------------------------------------------
>
> Key: FLINK-12362
> URL: https://issues.apache.org/jira/browse/FLINK-12362
> Project: Flink
> Issue Type: Bug
> Components: Deployment / YARN
> Reporter: vinoyang
> Assignee: vinoyang
> Priority: Major
>
> Recently, the {{-n}} config option has been removed from the document, the
> commit is here:
> [https://github.com/apache/flink/commit/60507b8baf5fba999b7c2c45c150914f38f5ce38#diff-8ae07fac4c1f4137fc1ef062aef70115L100]
> I can understand that maybe this option is useless for Flink session. But for
> job cluster mode, remove this option would confuse the users:
> * the {{-n}} has been deprecated and replaced with {{-p}}?
> * {{-p}} means the job level parallelism, but if users want to set a single
> operator's parallelism? how to calculate the number of containers
> * the {{-n}} option still exists in {{FlinkYarnSessionCli}}
> * we have customized the source code which broken the rule: one container
> one slot, so the {{-n}} is still useful
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
