[jira] [Commented] (SLIDER-109) Need a better indicator for application state/health

["Steve Loughran (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SLIDER-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14226204#comment-14226204 ] 

Steve Loughran commented on SLIDER-109:
---------------------------------------

the codahale metrics include healthchecks: small/fast function calls to return the health of a system. App health can be provided this way.

We also need to consider what the minimum no of instances of a component is needed for an app to consider itself live.

> Need a better indicator for application state/health
> ----------------------------------------------------
>
>                 Key: SLIDER-109
>                 URL: https://issues.apache.org/jira/browse/SLIDER-109
>             Project: Slider
>          Issue Type: Improvement
>          Components: agent-provider, appmaster
>    Affects Versions: Slider 0.40
>            Reporter: Sumit Mohanty
>            Assignee: Sumit Mohanty
>             Fix For: Slider 2.0.0
>
>
> Yarn Application state is different than the application state as perceived by Yarn. Such as:
> * When Yarn app state says RUNNING, the application deployed by Slider may actually be in the process of starting, and not yet ready for clients.
> * When Yarn app state says RUNNING, the application may in fact be unhealthy as in the component instances have gone down and waiting to come back up
> Application should be allowed to define its state (for its admin and clients) that is different than the application state as reported by Yarn.



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