[jira] [Commented] (MESOS-4925) Enhance Mesos filter to support filtering Mesos agent based on agent attribute
[ https://issues.apache.org/jira/browse/MESOS-4925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15218983#comment-15218983 ] Hans van den Bogert commented on MESOS-4925: Just wanted to note that this could come in handy for Spark's fine-grained mode as well. In fine-grained mode the spark driver should only have to receive CPU resources as its memory use is only allocated initially and not returned to mesos, unless the whole spark application is terminated. > Enhance Mesos filter to support filtering Mesos agent based on agent attribute > -- > > Key: MESOS-4925 > URL: https://issues.apache.org/jira/browse/MESOS-4925 > Project: Mesos > Issue Type: Improvement > Components: allocation >Reporter: Qian Zhang >Assignee: Qian Zhang > > Currently Mesos supports framework to set a filter when it accept an offer > (i.e., filter the unused resources in the offer) or when it decline an offer > (i.e., filter all the resources in the offer), and then allocator will not > send the filtered resources to framework within the configurable duration. > This is great. > However, there are also some use cases that framework may want to set a > filter based on agent attribute, e.g., framework does not want to receive > offers for any agents which does not have a specific attribute (e.g., GPU, > SSD, etc.). So I think we may need to enhance the Mesos filter to support > this kind of attribute-based filtering. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-4925) Enhance Mesos filter to support filtering Mesos agent based on agent attribute
[ https://issues.apache.org/jira/browse/MESOS-4925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15192833#comment-15192833 ] Klaus Ma commented on MESOS-4925: - Two more cases about the filter: 1. filter resources type; for example, if the tasks in framework only use cpu & memory, the master should only get the offer with cpu & memory 2. the framework decline resources instead of offers; if framework known its target tasks (e.g. only cpu & memory), it does not need to wait for offer and decline disk & port. Thanks Klaus > Enhance Mesos filter to support filtering Mesos agent based on agent attribute > -- > > Key: MESOS-4925 > URL: https://issues.apache.org/jira/browse/MESOS-4925 > Project: Mesos > Issue Type: Improvement > Components: allocation >Reporter: Qian Zhang >Assignee: Qian Zhang > > Currently Mesos supports framework to set a filter when it accept an offer > (i.e., filter the unused resources in the offer) or when it decline an offer > (i.e., filter all the resources in the offer), and then allocator will not > send the filtered resources to framework within the configurable duration. > This is great. > However, there are also some use cases that framework may want to set a > filter based on agent attribute, e.g., framework does not want to receive > offers for any agents which does not have a specific attribute (e.g., GPU, > SSD, etc.). So I think we may need to enhance the Mesos filter to support > this kind of attribute-based filtering. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
