From issues-return-148324-archive-asf-public=cust-asf.ponee.io@flink.apache.org Wed Jan 17 10:39:04 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id D67E018062C for ; Wed, 17 Jan 2018 10:39:04 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id C6C96160C35; Wed, 17 Jan 2018 09:39:04 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 1AF12160C1B for ; Wed, 17 Jan 2018 10:39:03 +0100 (CET) Received: (qmail 52054 invoked by uid 500); 17 Jan 2018 09:39:03 -0000 Mailing-List: contact issues-help@flink.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@flink.apache.org Delivered-To: mailing list issues@flink.apache.org Received: (qmail 52045 invoked by uid 99); 17 Jan 2018 09:39:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Jan 2018 09:39:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id AC640D3376 for ; Wed, 17 Jan 2018 09:39:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.711 X-Spam-Level: X-Spam-Status: No, score=-100.711 tagged_above=-999 required=6.31 tests=[RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id zWIWKRf5xliE for ; Wed, 17 Jan 2018 09:39:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id CB3F05FAE4 for ; Wed, 17 Jan 2018 09:39:00 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 591C3E0617 for ; Wed, 17 Jan 2018 09:39:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 15324212F5 for ; Wed, 17 Jan 2018 09:39:00 +0000 (UTC) Date: Wed, 17 Jan 2018 09:39:00 +0000 (UTC) From: "Dongwon Kim (JIRA)" To: issues@flink.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (FLINK-8431) Allow to specify # GPUs for TaskManager in Mesos MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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)