[ https://issues.apache.org/jira/browse/SLIDER-743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sumit Mohanty updated SLIDER-743: --------------------------------- Assignee: Sumit Mohanty > 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: Sumit Mohanty > Fix For: Slider 0.70 > > > 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)