[
https://issues.apache.org/jira/browse/MESOS-3401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14909652#comment-14909652
]
Qian Zhang commented on MESOS-3401:
-----------------------------------
[~greggomann], for the use cases you mentioned, I think the first thing we need
to consider is how to dynamically monitor and report labels in runtime, can we
support it for resources and attributes in agent now? So far, I think resources
and attributes are statically configured in agent startup which will not be
changed in runtime. To me, it seems another feature :-)
and I quickly went through the slides mentioned by [~haosd...@gmail.com] for
YARN's node labels feature, it seems for YARN, the label is also in node level
rather than resource level, so it is similar with the attribute of Mesos agent.
So I think the key question is, do we need to add the label in such a
fine-grained level (resource)? Can the existing attribute feature in agent
level meet our use cases? IMHO, adding label in resource may make things
complicated. My understanding is, resource is something can be consumed in
agent, attribute is like the metadata of the agent, they two work perfect to me
:-)
And another point I'd like to mention is, no matter we add the label in
resource or use the existing agent's attribute feature, it (label/attribute)
should not be used to affect how master offers resources, it should be used by
framework's scheduler for how it does the scheduling.
> Add labels to Resources
> -----------------------
>
> Key: MESOS-3401
> URL: https://issues.apache.org/jira/browse/MESOS-3401
> Project: Mesos
> Issue Type: Improvement
> Components: slave
> Reporter: Adam B
> Assignee: Greg Mann
> Labels: mesosphere, resources
>
> Similar to how we have added labels to tasks/executors (MESOS-2120), and even
> FrameworkInfo (MESOS-2841), we should extend Resource to allow arbitrary
> key/value pairs.
> This could be used to specify that a cpu resource has a certain speed, that a
> disk resource is SSD, or express any other metadata about a built-in or
> custom resource type. Only the scalar quantity will be used for determining
> fair share in the Mesos allocator. The rest will be passed onto frameworks as
> info they can use for scheduling decisions.
> This would require changes to how the slave specifies its `--resources`
> (probably as json), how the slave/master reports resources in its web/json
> API, and how resources are offered to frameworks.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
