[
https://issues.apache.org/jira/browse/SLIDER-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14177626#comment-14177626
]
Sumit Mohanty commented on SLIDER-109:
--------------------------------------
Two different requirements surfaced from discussions:
* How to know application is ready - by ready it may mean that the application
is ready to accept request. This could be based on the fact that a URL got
registered by the app or a specific component came up successfully.
* Using Status command is it possible to distinguish between Stopped vs.
Destroyed applications?
> 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)
