You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@slider.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2014/09/12 19:52:34 UTC

[jira] [Resolved] (SLIDER-403) Handle container failure threshold dynamically

     [ https://issues.apache.org/jira/browse/SLIDER-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steve Loughran resolved SLIDER-403.
-----------------------------------
    Resolution: Won't Fix

> Handle container failure threshold dynamically
> ----------------------------------------------
>
>                 Key: SLIDER-403
>                 URL: https://issues.apache.org/jira/browse/SLIDER-403
>             Project: Slider
>          Issue Type: Improvement
>            Reporter: Ted Yu
>         Attachments: slider-403.txt
>
>
> Basic windowed failure handling is in place.
> Steve made the following suggestion:
> You could specify a smaller number for failure threshold and still distinguish "broken app/configuration" from "unreliable cluster".
> During app package development, a failure threshold of 1 is probably appropriate
> basic windowed = we reset the counter after a configured interval. Whenever the cluster is flexed the counter is also reset



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)