You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@slider.apache.org by "Sumit Mohanty (JIRA)" <ji...@apache.org> on 2017/08/29 23:46:00 UTC
[jira] [Assigned] (SLIDER-109) Detect and report application
liveness
[ https://issues.apache.org/jira/browse/SLIDER-109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sumit Mohanty reassigned SLIDER-109:
------------------------------------
Assignee: (was: Sumit Mohanty)
> Detect and report application liveness
> --------------------------------------
>
> 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
> 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.4.14#64029)