[
https://issues.apache.org/jira/browse/SLIDER-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14956623#comment-14956623
]
Steve Loughran commented on SLIDER-82:
--------------------------------------
Extra complication: labels.
When a list of possible target nodes is calculated, it must only include those
which hold the labels associated with that role.
example, role "master" needs the label "static". After enumerating all nodes in
the cluster, all nodes which don't have that label must be stripped prior to
building the request. Otherwise you get an inconsistent constraint.
> 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
> Assignee: Steve Loughran
> Fix For: Slider 2.0.0
>
> Attachments: SLIDER-82.002.patch
>
>
> 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)
