[
https://issues.apache.org/jira/browse/MESOS-4027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15071886#comment-15071886
]
Qian Zhang commented on MESOS-4027:
-----------------------------------
And another finding is, there is a {{url}} field in the Offer message which can
be used to reach the Mesos agent, and each Mesos agent exposes an HTTP endpoint
{{/state}} which can be used to query some info about the agent, including the
tasks running on the agent, so I think when getting an offer from Mesos master,
framework can access the {{/state}} endpoint of the agent to know which tasks
are running on the agent, and then do the affinity/anti-affinity as it wants.
> 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
> Assignee: Qian Zhang
> 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)
