[
https://issues.apache.org/jira/browse/SLIDER-82?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajesh Kartha updated SLIDER-82:
--------------------------------
Attachment: SLIDER-82.002.patch
Added the null checks for roleHistory and role objects.
The patch does not cater to escalation
Also, performing flex for a component without ANTI_AFFINITY_REQUIRED after a
flex for a component *with* ANTI_AFFINITY_REQUIRED does not reset the
updateBlacklist() so the container does not get allocated.
I am yet to come across a way in the YARN API to reset the updateBlacklist() .
> 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
>
> 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)
