[jira] [Comment Edited] (TWILL-116) Support for start/stop/restart of a runnable in an application

["Henry Saputra (JIRA)" <ji...@apache.org>]

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

Henry Saputra edited comment on TWILL-116 at 6/23/15 2:54 AM:
--------------------------------------------------------------

Glad that this feature has good use case =)

I am thinking about having the Twill application master (AM) to be the proxy for the command to the runnable and use NMClient to de-allocoate new containers.

I am thinking that it would be cleaner than asking the particular runnable to update itself.


was (Author: hsaputra):
Thinking about having the Twill application master (AM) to be the proxy for the command to the runnable and use NMClient to de-allocoate new containers.

I am thinking that it would be cleaner than asking the particular runnable to update itself.

> Support for start/stop/restart of a runnable in an application
> --------------------------------------------------------------
>
>                 Key: TWILL-116
>                 URL: https://issues.apache.org/jira/browse/TWILL-116
>             Project: Apache Twill
>          Issue Type: New Feature
>          Components: core
>            Reporter: Albert Shau
>            Assignee: Henry Saputra
>             Fix For: 0.6.0-incubating
>
>         Attachments: TWILL-116-design.pdf
>
>
> Once an application is running, it would be good to be able to stop, start, and restart a specific runnable of the application without affecting other runnables.  
> For example, I may be running multiple services in a single application, with each service as a different runnable. One of my services gets into an invalid state. I now want to restart just that runnable and not the other ones that are running properly.



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