[
https://issues.apache.org/jira/browse/SLIDER-494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16110611#comment-16110611
]
kyungwan nam commented on SLIDER-494:
-------------------------------------
We have a need for this. so, I have worked on a patch for this.
* an application has a workType property - SERVICE (default), BATCH
* each component has a workType property - SERVICE (default), BATCH
* increment the batchCompleted in the RoleStatus, when a component instance
whose workType is BATCH has been completed successfully. (It means that START
command has been succeed with 0 exit-code). and componentTag
(app_container_tag) assigned to that must not be assigned no longer.
condition to stop application.
* the application must be BATCH workType.
* at least, one component must be BATCH workType.
* for all component whose workType is BATCH, the batchCompleted in the
RoleStatus matched the number of instances requested.
cautions
* component/commandScript/timeout must be set properly. it determine that how
long BATCH job take.
* when AM is restarted, the batchCompleted will be lost. in that case, batch
component re-execute except running containers.
> 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.4.14#64029)
