[
https://issues.apache.org/jira/browse/SLIDER-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14957186#comment-14957186
]
Thomas Weise commented on SLIDER-82:
------------------------------------
Since the new approach relies on requesting specific nodes instead of
blacklisting: Working on Apache Apex we have seen issues requesting specific
nodes on CDH up till the last release. We have seen the same issue testing KOYA
on CDH with component recovery:
https://mail-archives.apache.org/mod_mbox/incubator-slider-dev/201505.mbox/%3cd1823655.e319%25gs...@hortonworks.com%3E
I can volunteer to test the patch on CDH.
> 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
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> 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)
