[
https://issues.apache.org/jira/browse/FLINK-8431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16331252#comment-16331252
]
ASF GitHub Bot commented on FLINK-8431:
---------------------------------------
Github user EronWright commented on a diff in the pull request:
https://github.com/apache/flink/pull/5307#discussion_r162462667
--- Diff: flink-mesos/pom.xml ---
@@ -88,7 +88,7 @@ under the License.
<dependency>
<groupId>com.netflix.fenzo</groupId>
<artifactId>fenzo-core</artifactId>
- <version>0.9.3</version>
+ <version>0.10.0</version>
--- End diff --
My number one concern is the impact of updating the Fenzo dependency.
You're taking a conservative approach here, which is probably wise. But I
also have an aversion to `.0` releases. Can we compromise and use `0.10.1`?
Meanwhile I am reviewing the Fenzo changelog.
> Allow to specify # GPUs for TaskManager in Mesos
> ------------------------------------------------
>
> Key: FLINK-8431
> URL: https://issues.apache.org/jira/browse/FLINK-8431
> Project: Flink
> Issue Type: Improvement
> Components: Cluster Management, Mesos
> Reporter: Dongwon Kim
> Assignee: Dongwon Kim
> Priority: Minor
>
> Mesos provides first-class support for Nvidia GPUs [1], but Flink does not
> exploit it when scheduling TaskManagers. If Mesos agents are configured to
> isolate GPUs as shown in [2], TaskManagers that do not specify to use GPUs
> cannot see GPUs at all.
> We, therefore, need to introduce a new configuration property named
> "mesos.resourcemanager.tasks.gpus" to allow users to specify # of GPUs for
> each TaskManager process in Mesos.
> [1] http://mesos.apache.org/documentation/latest/gpu-support/
> [2] http://mesos.apache.org/documentation/latest/gpu-support/#agent-flags
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
