You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@mesos.apache.org by "Chris (JIRA)" <ji...@apache.org> on 2015/11/30 23:04:11 UTC

[jira] [Comment Edited] (MESOS-4027) Improve task-node affinity

    [ https://issues.apache.org/jira/browse/MESOS-4027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15032577#comment-15032577 ] 

Chris edited comment on MESOS-4027 at 11/30/15 10:04 PM:
---------------------------------------------------------

I've developed a patch in support of this ticket (it's been pushed to my github mesos fork). The patch requires testing (among other things - ie: a Shepard) before submitting for review.


was (Author: ct.clmsn):
I've developed a patch for in support of this ticket. The patch requires testing (among other things - ie: a Shepard) before submitting for review.

> 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)