[
https://issues.apache.org/jira/browse/SLIDER-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14984374#comment-14984374
]
Steve Loughran commented on SLIDER-82:
--------------------------------------
status: I've just merged the ongoing work into develop. This does not address
anti-affinity at all, and SLIDER-947 is outstanding; we'll need to stand up a
YarnClient in the AM to bootstrap the state. (mock cluster tests will need to
mimic this). I've merged it in to keep delta between feature and app branch low.
What is in are
* ongoing patches during the process: SLIDER-948, SLIDER-943
* All RoleHistory state is now published as metrics. That's part of my plan for
metrics-based testing: publish state to metrics, and test runners poll those
metrics to determine internal state of app.
* nodemap is published via REST and IPC.
> 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)
