Return-Path: X-Original-To: apmail-mesos-user-archive@www.apache.org Delivered-To: apmail-mesos-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B675117988 for ; Wed, 9 Sep 2015 04:09:43 +0000 (UTC) Received: (qmail 99274 invoked by uid 500); 9 Sep 2015 04:09:43 -0000 Delivered-To: apmail-mesos-user-archive@mesos.apache.org Received: (qmail 99137 invoked by uid 500); 9 Sep 2015 04:09:42 -0000 Mailing-List: contact user-help@mesos.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@mesos.apache.org Delivered-To: mailing list user@mesos.apache.org Received: (qmail 99127 invoked by uid 99); 9 Sep 2015 04:09:42 -0000 Received: from Unknown (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Sep 2015 04:09:42 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 71BAB18099B for ; Wed, 9 Sep 2015 04:09:42 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.899 X-Spam-Level: ** X-Spam-Status: No, score=2.899 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=3, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id Qy_v4hxZf55m for ; Wed, 9 Sep 2015 04:09:36 +0000 (UTC) Received: from mail-io0-f182.google.com (mail-io0-f182.google.com [209.85.223.182]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTPS id 9F7EE44151 for ; Wed, 9 Sep 2015 04:09:36 +0000 (UTC) Received: by iofh134 with SMTP id h134so8641031iof.0 for ; Tue, 08 Sep 2015 21:09:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=Q2oQszSFXwItDkSensfFfuE2KPI2ozJSCkykgu3tyQA=; b=gJrr00o3FFqCp9x4kO433hDChshJ2/OnFTZjtX6lHQPSXcsKcZelY6pgKwRsuGrBQl gNOPdMwAXoxIpCtmlFzf/f8+B5TPUP5DOo6rcSuLqWW59DPkw6wcQ3znlLO2WDwDoJBX /ybUdzG/gi95nfGiWXq4ft2KrXMYOSXN+KhM5J0sTT9+1aN8hzKMLSLAhjoyNmOieFHF cQmS13hyDx26A367FpGkCLJYkLOHgvoZxMKPvLjV4o7rxZTmEbcqb4eOA+H6bUvezsPF DNCBmgU/VQqUsbj8qCUpvYZQY1GEAthcxw7IzhsfZrr4gKqFZT5881/OgzkTIf5uIGTD jrYw== MIME-Version: 1.0 X-Received: by 10.107.160.143 with SMTP id j137mr22447611ioe.13.1441771776136; Tue, 08 Sep 2015 21:09:36 -0700 (PDT) Received: by 10.36.95.143 with HTTP; Tue, 8 Sep 2015 21:09:36 -0700 (PDT) In-Reply-To: References: Date: Tue, 8 Sep 2015 23:09:36 -0500 Message-ID: Subject: Re: Setting maximum per-node resources in offers From: RJ Nowling To: user@mesos.apache.org Content-Type: multipart/alternative; boundary=001a114043d6905b54051f48a659 --001a114043d6905b54051f48a659 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Thanks, Klaus. I think I was probably misunderstanding the role of the allocator in Mesos versus the scheduler in the framework sitting on top of Mesos. Probably out of scope for Mesos to divide up resources as I was suggesting. On Tue, Sep 8, 2015 at 10:48 PM, Klaus Ma wrote: > If it's the only framework, you will receive all nodes from Mesos as > offers. You can re-schedule those resources to run tasks on each node. > > > On 2015=E5=B9=B409=E6=9C=8809=E6=97=A5 03:03, RJ Nowling wrote: > >> Hi all, >> >> I have a smallish cluster with a lot of cores and RAM per node. I want >> to support multiple users so I'd like to set up Mesos to provide a maxim= um >> of 8 cores per node in the resource offers. Resource offers should incl= ude >> multiple nodes to reach the requirements of the user. For example, if t= he >> user requests 32 cores, I would like 8 cores from each of 4 nodes. >> >> Is this possible? Or can someone suggest alternatives? >> >> Thanks, >> RJ >> > > -- > Klaus Ma (=E9=A9=AC=E8=BE=BE), PMP=C2=AE | http://www.cguru.net > > --001a114043d6905b54051f48a659 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Thanks, Klaus.

I think I was probably m= isunderstanding the role of the allocator in Mesos versus the scheduler in = the framework sitting on top of Mesos.=C2=A0 Probably out of scope for Meso= s to divide up resources as I was suggesting.

On Tue, Sep 8, 2015 at 10:48 PM, Kl= aus Ma <klaus@cguru.net> wrote:
If it's the only framework, you will receive all nodes from Mesos a= s offers. You can re-schedule those resources to run tasks on each node.


On 2015=E5=B9=B409=E6=9C=8809=E6=97=A5 03:03, RJ Nowling wrote:
Hi all,

I have a smallish cluster with a lot of cores and RAM per node.=C2=A0 I wan= t to support multiple users so I'd like to set up Mesos to provide a ma= ximum of 8 cores per node in the resource offers.=C2=A0 Resource offers sho= uld include multiple nodes to reach the requirements of the user.=C2=A0 For= example, if the user requests 32 cores, I would like 8 cores from each of = 4 nodes.

Is this possible?=C2=A0 Or can someone suggest alternatives?

Thanks,
RJ

--
Klaus Ma (=E9=A9=AC=E8=BE=BE), PMP=C2=AE | http://www.cguru.net


--001a114043d6905b54051f48a659--