[
https://issues.apache.org/jira/browse/SLIDER-743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14299480#comment-14299480
]
ASF subversion and git services commented on SLIDER-743:
--------------------------------------------------------
Commit 39e04e36ed72e8a40434e82db0d7f0f210f26f1d in incubator-slider's branch
refs/heads/develop from [~sumitmohanty]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-slider.git;h=39e04e3 ]
SLIDER-743. Include node failure history when choosing placement hints
> Include node failure history when choosing placement hints
> ----------------------------------------------------------
>
> Key: SLIDER-743
> URL: https://issues.apache.org/jira/browse/SLIDER-743
> Project: Slider
> Issue Type: Improvement
> Components: appmaster
> Affects Versions: Slider 0.60
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Fix For: Slider 0.70
>
> Attachments: SLIDER-743.patch
>
>
> Use the (collected) history on per-node failures to tune placement requests,
> so that even if there's a history of components running there, if its been
> failing recently then it's not asked for
> # Add a "recent failures" field to the node entries, alongside the "total
> failures" counter
> # the scheduled failure count resetter will set that field to zero,alongside
> the component failures
> # When Slider has to request a new container, if a node has a recent failure
> count above some threshold, it will not be requested, even if it is a past
> location of that component.
> When the placement policy is STRICT, node failure history will not be taken
> into account
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
