[
https://issues.apache.org/jira/browse/MESOS-4027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15053934#comment-15053934
]
Qian Zhang commented on MESOS-4027:
-----------------------------------
[~ct.clmsn] I understand your requirement, but that means a framework could be
able to know what the tasks are running in an agent even some of the tasks
belong to other frameworks, I am not sure if this is OK from multi-tenant and
security point of view, e.g., a framework may not want other frameworks to know
anything about its tasks.
Maybe we could leave the decision to framework itself, e.g., when framework
launches a task, it can decide it is a "public" or "private" task, and if it is
"public", then task's label will be propagated into an offer, so any framework
receives that offer will know that "public" task already running on that agent.
> 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)
