Mailing-List: contact issues-help@mesos.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@mesos.apache.org
Date: Tue, 23 Aug 2016 04:52:20 +0000 (UTC)
From: "Benjamin Mahler (JIRA)" <jira@apache.org>
To: issues@mesos.apache.org
Message-ID: <JIRA.12999103.1471924941000.379630.1471927940831@Atlassian.JIRA>
In-Reply-To: <JIRA.12999103.1471924941000@Atlassian.JIRA>
References: <JIRA.12999103.1471924941000@Atlassian.JIRA> <JIRA.12999103.1471924941252@arcas>
Subject: [jira] [Updated] (MESOS-6071) Validate that an explicitly specified
 DEFAULT executor has disk resources.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 23 Aug 2016 04:52:22 -0000


     [ https://issues.apache.org/jira/browse/MESOS-6071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benjamin Mahler updated MESOS-6071:
-----------------------------------
    Summary: Validate that an explicitly specified DEFAULT executor has disk resources.  (was: Validate that an explicitly specified DEFAULT executor has resources.)

> Validate that an explicitly specified DEFAULT executor has disk resources.
> --------------------------------------------------------------------------
>
>                 Key: MESOS-6071
>                 URL: https://issues.apache.org/jira/browse/MESOS-6071
>             Project: Mesos
>          Issue Type: Task
>          Components: master
>            Reporter: Benjamin Mahler
>
> When the framework is explicitly specifying the DEFAULT executor (currently only supported for task groups), we should consider validating that it contains disk resources.
> We should also consider supporting the omission of DEFAULT executor resources and injecting a default amount of resources. However, the difficulty here is that the framework must know about these amounts since they need to be available in the offer. We could expose these to the framework during framework registration.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)