[
https://issues.apache.org/jira/browse/SLIDER-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14118638#comment-14118638
]
ASF subversion and git services commented on SLIDER-327:
--------------------------------------------------------
Commit e7dd217a324c205826bea4ac040b808c4ad72d61 in incubator-slider's branch
refs/heads/develop from [[email protected]]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-slider.git;h=e7dd217 ]
Merge branch
'feature/SLIDER-327_AM_to_move_to_optimized,_queued_Node_review_and_refresh_action'
into develop
> AM to move to optimized, queued Node review and refresh action
> --------------------------------------------------------------
>
> Key: SLIDER-327
> URL: https://issues.apache.org/jira/browse/SLIDER-327
> Project: Slider
> Issue Type: Improvement
> Affects Versions: Slider 0.50
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Fix For: Slider 0.60
>
>
> The {{reviewRequestAndReleaseNodes()}} operation should be converted to an
> async action, with all operations/triggers for review posting it in with a
> short (1s? delay).
> The executor should not only call the AM, it can be clever about optimising
> its workload
> # if there are events in the queue marked as changing cluster size, the
> review should come after them.
> # if there is an existing review operations in the queue, there's no need to
> schedule a new one.
> Having a delay means that a sequence of container failure events coming in
> one after the other don't trigger lots of reviews
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
