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 D753310590 for ; Mon, 9 Feb 2015 10:35:57 +0000 (UTC) Received: (qmail 14691 invoked by uid 500); 9 Feb 2015 10:35:57 -0000 Delivered-To: apmail-mesos-user-archive@mesos.apache.org Received: (qmail 14644 invoked by uid 500); 9 Feb 2015 10:35:57 -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 14634 invoked by uid 99); 9 Feb 2015 10:35:57 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Feb 2015 10:35:57 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of codecraig@gmail.com designates 209.85.223.176 as permitted sender) Received: from [209.85.223.176] (HELO mail-ie0-f176.google.com) (209.85.223.176) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Feb 2015 10:35:52 +0000 Received: by iecrp18 with SMTP id rp18so8938088iec.7 for ; Mon, 09 Feb 2015 02:34:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=S6P4XCYvJY5++kHDsfXnHbQK99sIVmSSKZiae7NtmMA=; b=wso1T9rB+xodhEDSOM4rmyL6w5Mh/PSIPwf20ywvlxCquSfrQDjLQCLbajX975pEhq 3NlXXsyQ/g82yGIRlvqDtH1H2vrQeI5XNwg+jpxreCK0f8UmKq5o25kWGsszKYwmRofD BiXVmwcz8oPIUtqknSZp1J4GmFHefVJuz58aRQ6qVs7yTX4G+vWqUE7bDb1vtGc+mXhe hIWV2PRc0wyJP3dzBbkZ0ibUM19XpWkrucgUNzqUKwYO1AUzocDxNB47AfFXCwcfctFf 4A5jhDr4CpY9e32p8vJxm0agHaC4CnHSnZaT8ewXp+jd0OGmaWpJX7YekpZNd/ZasSU/ zUDg== MIME-Version: 1.0 X-Received: by 10.107.36.12 with SMTP id k12mr15885052iok.41.1423478086509; Mon, 09 Feb 2015 02:34:46 -0800 (PST) Received: by 10.36.37.73 with HTTP; Mon, 9 Feb 2015 02:34:46 -0800 (PST) Date: Mon, 9 Feb 2015 05:34:46 -0500 Message-ID: Subject: Total resources available versus actually available From: craig w To: user@mesos.apache.org Content-Type: multipart/alternative; boundary=001a11403ab2b12df2050ea551f9 X-Virus-Checked: Checked by ClamAV on apache.org --001a11403ab2b12df2050ea551f9 Content-Type: text/plain; charset=UTF-8 Mesos slaves report the total resources they have available, such as 2 CPU, 8GB Memory and 100GB disk. Does Mesos keep track of the amount of resources that are actually available to best schedule tasks? For example, imagine a slave has some other processes running on it (that are not mesos tasks) that are taking up 6GB of RAM (out of the total 8GB). A new task is created in Mesos that needs 4GB of RAM, would Mesos still try to put the new task on the slave? --001a11403ab2b12df2050ea551f9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Mesos slaves report the total resources they have ava= ilable, such as 2 CPU, 8GB Memory and 100GB disk.

Does Mesos k= eep track of the amount of resources that are actually available to best sc= hedule tasks?

For example, imagine a slave has some other processes= running on it (that are not mesos tasks) that are taking up 6GB of RAM (ou= t of the total 8GB). A new task is created in Mesos that needs 4GB of RAM, = would Mesos still try to put the new task on the slave?
--001a11403ab2b12df2050ea551f9--