You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@slider.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2014/08/12 15:21:13 UTC
[jira] [Commented] (SLIDER-77) use a window for tracking container
failures
[ https://issues.apache.org/jira/browse/SLIDER-77?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14094044#comment-14094044 ]
ASF subversion and git services commented on SLIDER-77:
-------------------------------------------------------
Commit 1617468 from [~stevel@apache.org] in branch 'site/trunk'
[ https://svn.apache.org/r1617468 ]
SLIDER-77 document windowed failure policy
> 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)