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 2015/01/09 02:11:35 UTC

[jira] [Commented] (SLIDER-723) Memcached component launch fail does not propagate

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

Sumit Mohanty commented on SLIDER-723:
--------------------------------------

Reproduced the scenario:
* Container fails at the INSTALL step
* The agent's logic to monitor process health only starts after the START is issued
* Agent reports back failure to AM and AM issues 2 more retries (default behavior)

In the end the agent remains running as it does not have to logic to go down in case of install failures. Its a BUG.

Agent needs to go down if INSTALL fails.

> Memcached component launch fail does not propagate
> --------------------------------------------------
>
>                 Key: SLIDER-723
>                 URL: https://issues.apache.org/jira/browse/SLIDER-723
>             Project: Slider
>          Issue Type: Improvement
>    Affects Versions: Slider 0.60
>            Reporter: Yang Hao
>
> When am applies a container for the component ,and the container starts, but the component may not launch successfully. So a friendly way should be out. Like just kill the container when the component don't launch successfully.



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