[ 
https://issues.apache.org/jira/browse/SLIDER-967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15002563#comment-15002563
 ] 

ASF subversion and git services commented on SLIDER-967:
--------------------------------------------------------

Commit 5a61b4cd8189ae02eb9eaeb8ffdb25604dcc4376 in incubator-slider's branch 
refs/heads/feature/SLIDER-82-pass-3.1 from [[email protected]]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-slider.git;h=5a61b4c ]

SLIDER-967 AA placement with nodemap updates working


> Use nodemap to build up location restrictions on AA placement
> -------------------------------------------------------------
>
>                 Key: SLIDER-967
>                 URL: https://issues.apache.org/jira/browse/SLIDER-967
>             Project: Slider
>          Issue Type: Sub-task
>          Components: appmaster
>    Affects Versions: Slider 0.90
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>             Fix For: Slider 0.90
>
>   Original Estimate: 8h
>  Remaining Estimate: 8h
>
> This is the key AA placement work:  AA placement requests to use nodemap to 
> build up the explicit list of suitable nodes, while excluding
> # all nodes where there's an instance already
> # all nodes with an outstanding request
> # all nodes considered failed
> For now, let's include those considered "unreliable", as in having launches 
> fail recently.
> The list to submit should be *all nodes with the target label expression*. 
> This means that we'll have to use the label information in the nodemap and 
> requests & do some matching in the AM first.
> Also: stop listing all the changed  nodes on a nodemap update...just the 
> first 10 should be enough.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to