[jira] [Commented] (MESOS-6071) Validate that an explicitly specified DEFAULT executor has disk resources.

2016-08-23 Thread Vinod Kone (JIRA)

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

Vinod Kone commented on MESOS-6071:
---

The current validation code checks that task group executors have non-zero disk 
resources. 
https://github.com/apache/mesos/blob/master/src/master/validation.cpp#L1080

Is this ticket supposed to track something else?

> 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)


[jira] [Commented] (MESOS-6071) Validate that an explicitly specified DEFAULT executor has disk resources.

2016-08-23 Thread Abhishek Dasgupta (JIRA)

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

Abhishek Dasgupta commented on MESOS-6071:
--

Is anyone actively working on this? I would like to take up this issue.
cc [~bmahler]

> 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)


[jira] [Commented] (MESOS-6071) Validate that an explicitly specified DEFAULT executor has disk resources.

2016-08-23 Thread Abhishek Dasgupta (JIRA)

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

Abhishek Dasgupta commented on MESOS-6071:
--

Is anyone actively working on this? I would like to take up this issue.
cc [~bmahler]

> 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)