[
https://issues.apache.org/jira/browse/FLINK-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15135750#comment-15135750
]
ASF GitHub Bot commented on FLINK-2213:
---------------------------------------
Github user rmetzger commented on a diff in the pull request:
https://github.com/apache/flink/pull/1588#discussion_r52101633
--- Diff: docs/setup/config.md ---
@@ -211,6 +211,8 @@ The parameters define the behavior of tasks that create
result files.
yarn.application-master.env.LD_LIBRARY_PATH: "/usr/lib/native"
+- `yarn.containers.vcores` The number of virtual cores (vcores) per YARN
container. By default the number of `vcores` is set equal to the maximum
between the number of slots per TaskManager, and the number of cores available
to the Java runtime.
--- End diff --
what's the rationale for using the max(slots, #cpus) ?
I think in most cases users use fewer slots than CPU cores available on the
physical machine.
> Configure number of vcores
> --------------------------
>
> Key: FLINK-2213
> URL: https://issues.apache.org/jira/browse/FLINK-2213
> Project: Flink
> Issue Type: Improvement
> Components: YARN Client
> Affects Versions: 0.10.0
> Reporter: Ufuk Celebi
> Assignee: Kostas
> Fix For: 1.0.0
>
>
> Currently, the number of vcores per YARN container is set to 1.
> It is desirable to allow configuring this value. As a simple heuristic it
> makes sense to at least set it to the number of slots per container.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
