You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@slider.apache.org by "Weiwei Yang (JIRA)" <ji...@apache.org> on 2015/05/12 10:03:00 UTC

[jira] [Issue Comment Deleted] (SLIDER-82) Support ANTI_AFFINITY_REQUIRED option

     [ https://issues.apache.org/jira/browse/SLIDER-82?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Weiwei Yang updated SLIDER-82:
------------------------------
    Comment: was deleted

(was: Hello [~steve_l]

Would this jira be an alternative of YARN-1042 ? Say, Apps can request anti-affinity containers from yarn if it is done by slider.)

> Support ANTI_AFFINITY_REQUIRED option
> -------------------------------------
>
>                 Key: SLIDER-82
>                 URL: https://issues.apache.org/jira/browse/SLIDER-82
>             Project: Slider
>          Issue Type: Task
>          Components: appmaster
>            Reporter: Steve Loughran
>             Fix For: Slider 2.0.0
>
>
> slider has an anti-affinity flag in roles (visible in resources.json?), which is ignored.
> YARN-1042 promises this for YARN, slider will need
> # flag in resources.json
> # use in container requests
> we may also want two policies: anti-affinity-desired, and -required. Then if required nodes get >1 container for the same component type on the same node, it'd have to request a new one and return the old one (Risk: getting the same one back). 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)