[
https://issues.apache.org/jira/browse/MESOS-6071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Mahler updated MESOS-6071:
-----------------------------------
Description:
When the framework is explicitly specifying the DEFAULT executor (currently
only supported for task groups), we should consider validating that it contains
disk resources. Currently, we validate that explicitly specified (DEFAULT or
CUSTOM) executors only contain cpus and mem.
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.
was:
When the framework is explicitly specifying the DEFAULT executor (currently
only supported for task groups), we should consider validating that it contains
disk resources. Currently, we validate that executors only contain cpus and mem.
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.
> 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. Currently, we validate that explicitly specified
> (DEFAULT or CUSTOM) executors only contain cpus and mem.
> 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)
