[
https://issues.apache.org/jira/browse/TWILL-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14598453#comment-14598453
]
Henry Saputra commented on TWILL-116:
-------------------------------------
I believe the NM will try to send regular Java termination which will call the
stop() method of your Runnable. But just in case the container is hang or
corrupted it may send SIGKILL signal which may not call the stop() method.
> 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-2.pdf, TWILL-116-design-3.pdf,
> 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)
