[ 
https://issues.apache.org/jira/browse/FLINK-8431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16328547#comment-16328547
 ] 

Dongwon Kim commented on FLINK-8431:
------------------------------------

[~eronwright] What I need to do next is to cope with the new Mesos components 
that are proposed by FLIP-6. I found flink-1.5-SNAPSHOT has two other scripts, 
{{mesos-appmaster-flip6-job.sh}} and  {{mesos-appmaster-flip6-session.sh}} 
besides {{mesos-appmaster.sh}}. I want to know how it works by executing them 
but I cannot find any document. 

* Is further modification needed to cope with FLIP-6 components?
* Can you explain how to execute FLIP-6 components? I cannot find any document 
regarding {{mesos-appmaster-flip6-job.sh}} and  
{{mesos-appmaster-flip6-session.sh}}.
* When I execute {{mesos-appmaster-flip6-session.sh}}, a new framework appears 
in Mesos UI but there's no hyperlink to the framework. Is this the dispatcher 
introduced in Flink-1.5?    

> 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)

Reply via email to