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

Yan Xu commented on MESOS-6219:
-------------------------------

Looks like we can achieve this by delaying the validation of resources until 
after the auto-detection is done to allow us to differentiate 

1. Explicitly specifying a resource with a zero value.
3. Explicitly specifying a resource without a value.
2. Not specifying the resource.

2, 3 are interpreted as auto-detection for certain predefined kinds of 
resources.

> Improve auto-detection of predefined resource types.
> ----------------------------------------------------
>
>                 Key: MESOS-6219
>                 URL: https://issues.apache.org/jira/browse/MESOS-6219
>             Project: Mesos
>          Issue Type: Improvement
>          Components: containerization
>            Reporter: Yan Xu
>
> Mesos agent currently auto-detects certain predefined resource types when 
> they are not specified. These include cpus, mem, (root) disk, gpus and also 
> MESOS-6062 is adding auto-detection for mount disks when the size is 
> specified as a special value "0". 
> Due to the limitation of the {{Resources}} abstraction the caller of 
> {{Resources::parse()}} can't tell if a resource is intentionally specified 
> with an empty value or unspecified. The current resource auto-detection in 
> {{Containerizer::resources()}} resorts to scanning the {{--resources}} flag 
> to check if a resource is specified, this is very fragile, e.g., it would 
> think {{gpus:0}} is specified (and not auto-detected) if there is a mount 
> disk with its root being {{/biggpush}}.
> It would be nice if we can have the user explicitly specify the intention to 
> have value of a standard resource auto-detected (at least with the JSON 
> input).



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

Reply via email to