[
https://issues.apache.org/jira/browse/UIMA-1109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jerry Cwiklik closed UIMA-1109.
-------------------------------
Resolution: Fixed
Modified to support orderly shutdown of a Uima AS service. The shutdown will be
initiated via JMX from a JMX admin application, like jConsole. A user first
connects to a remote (or local) JMX Server and navigates to the Uima AS top
level MBean. Each top level Uima AS service registers a new JMX MBean:
ControllerMBean. The new MBean exposes two methods:
- completeProcessingAndStop()
- stopNow()
The first method is used to initiate an orderly shutdown. When this method is
called, the top level service will stop all listeners on its input queue
(GetMeta and Process) and will keep the listeners on reply queues running. A
callback is registered with the InProcessCache that will be called as soon as
the cache becomes empty. This is an indication that all CASes have been fully
processed and only than, the service proceeds to shutdown. Since the orderly
shutdown requires that all CASes are fully processed, it may take some time
before the service actually shuts down.
The second method is used to initiate a immediate shutdown of a service. In
this case all listeners will be stopped and all CASes will be discarded.
> 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.
