[
https://issues.apache.org/jira/browse/SLIDER-77?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14094650#comment-14094650
]
ASF subversion and git services commented on SLIDER-77:
-------------------------------------------------------
Commit cc37299de2e5c5992430ea192de38334a7621d0f in incubator-slider's branch
refs/heads/feature/SLIDER-285_Restart_AM from [[email protected]]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-slider.git;h=cc37299 ]
SLIDER-77 : extra log statement triggering OOBE on launch with no args
> use a window for tracking container failures
> --------------------------------------------
>
> Key: SLIDER-77
> URL: https://issues.apache.org/jira/browse/SLIDER-77
> Project: Slider
> Issue Type: Sub-task
> Components: appmaster
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Minor
> Time Spent: 5h
> Remaining Estimate: 1h
>
> Use sliding windows and/or weighted moving averages to track container
> failures over time, and only react if many are failing in a short period.
> What we do want to do here is react fast to a sudden series of failures, as
> well as look at average failure rates over time. I think separating startup
> failures from operational failures could help here. We don't want 5 failures
> in 5 minutes to be ignored just because everything worked well for the
> previous month
--
This message was sent by Atlassian JIRA
(v6.2#6252)
