[
https://issues.apache.org/jira/browse/MESOS-4027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15052902#comment-15052902
]
Chris commented on MESOS-4027:
------------------------------
[~qianzhang] just noticed that - really should have spent more time reviewing
the documentation in the protobuf file. I'd like to see the Task's labels field
get propogated into an Offer so customized schedulers can have some view into
what is running on a Mesos Node (ie: scheduler logic may filter out Offers
associated with Nodes involved in Spark processing OR maybe schedulers want to
filter out Offers that are not associated with HDFS). Figured out a way to do
this without added more fields into the protobuf IDL for TaskInfo. Thanks for
pointing this out!!!
> Improve task-node affinity
> --------------------------
>
> Key: MESOS-4027
> URL: https://issues.apache.org/jira/browse/MESOS-4027
> Project: Mesos
> Issue Type: Wish
> Components: allocation, general
> Reporter: Chris
> Priority: Trivial
>
> Improve task-to-node affinity and anti-affinity (running hadoop or spark jobs
> on a node currently running hdfs or to avoid running Ceph on HDFS nodes).
> Provide a user-mutable Attribute in TaskInfo (the Attribute is modified by a
> Framework Scheduler) that can describe what a Task is running.
> The Attribute would propagate to a Task at execution. The Attribute is
> passed to Framework Schedulers as part of an Offer's Attributes list.
> A Framework Scheduler could then filter out or accept Offers from Nodes that
> are currently labeled with a desired set or individual Attribute.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
