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

Posted to dev@slider.apache.org by "Beckham007 (JIRA)" <ji...@apache.org> on 2014/11/20 03:12:33 UTC

[jira] [Commented] (SLIDER-494) Support for short-lived services

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

Beckham007 commented on SLIDER-494:
-----------------------------------

We can assign a "componentType" for each component. The componentType is batch(short lived service) or service(long lived service). When component exit code is zero and the componentType is batch, the component finishes normally(The Slider Agent could get the exit code of component?). Otherwise, the Slider AppMaster should retry it.

> Support for short-lived services
> --------------------------------
>
>                 Key: SLIDER-494
>                 URL: https://issues.apache.org/jira/browse/SLIDER-494
>             Project: Slider
>          Issue Type: Bug
>          Components: app-package, appmaster
>    Affects Versions: Slider 0.50
>            Reporter: Sumit Mohanty
>             Fix For: Slider 2.0.0
>
>
> Slider applications could be short lived in the sense that the component instances are not daemons but are processes that stop after they are done. These processes may also fail in which case they may be auto-restarted or they can complete gracefully in which case the application instance should terminate (when all component instances are complete).



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