[
https://issues.apache.org/jira/browse/SLIDER-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15022516#comment-15022516
]
ASF subversion and git services commented on SLIDER-82:
-------------------------------------------------------
Commit 076ecb1d00dafa7030e0facade283f41fa86e43b in incubator-slider's branch
refs/heads/develop from [~ste...@apache.org]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-slider.git;h=076ecb1 ]
SLIDER-82 TestBuildStandaloneAM.testUpgrade is failing in its post-run checks,
because the new role is being declared as outstanding. Disabling the check
entirely
> 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 0.90
>
> 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)
