[
https://issues.apache.org/jira/browse/UIMA-1109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12688720#action_12688720
]
Burn Lewis commented on UIMA-1109:
----------------------------------
I don't think we need to support client-initiated shutdown until we have a way
for clients to deploy remote services. One use case would be when moving a
service to a different machine -- first deploy on the new machine and then
gracefully undeploy on the old machine so that no work is lost. Another would
be when upgrading a service or UIMA-AS.
Currently services are started with deployAsyncService so we need a matching
undeploy that would be run from the same machine that would cause the service
to stop processing input requests and shutdown when the current request has
been completed. For simplicity it should apply to all instances of the service
started by the deploy script, so could use the pid of the JVM and a special
signal, but may not be able to rely on the shutdown hook since the logs may
have been closed ... but perhaps we can add a Java signal handler.
> Need ability to quiesce an instance of a service
> ------------------------------------------------
>
> Key: UIMA-1109
> URL: https://issues.apache.org/jira/browse/UIMA-1109
> Project: UIMA
> Issue Type: Improvement
> Components: Async Scaleout
> Reporter: Burn Lewis
>
> We can deploy extra instances of a service seamlessly but also need a
> mechanism to undeploy without losing any work, i.e. ask an instance to stop
> processing messages and shutdown when it finishes its current work.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
