[ 
https://issues.apache.org/jira/browse/UIMA-3704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jim Challenger closed UIMA-3704.
--------------------------------

    Resolution: Fixed

> DUCC SM should support timestamps to identify idle services
> -----------------------------------------------------------
>
>                 Key: UIMA-3704
>                 URL: https://issues.apache.org/jira/browse/UIMA-3704
>             Project: UIMA
>          Issue Type: Improvement
>          Components: DUCC
>    Affects Versions: 1.1.0-Ducc
>            Reporter: Jim Challenger
>            Assignee: Jim Challenger
>            Priority: Minor
>             Fix For: 1.1.0-Ducc
>
>
> The Service Manager's ping/monitor protocol should support a mechanism to 
> provide identification of services that are started and using resources, but 
> which have been idle for a "long time".  The mechanism should enable 
> identification of idle services and a mechanism to turn off the services 
> under site policies.
> The proposed mechanism is for the ping/monitors to support a "last use" 
> timestamp which indicates the last apparent use of the service.  Display 
> mechanisms such as the web server would use this to identify unused or 
> lightly-used services.  
> The mechanism also should enable ping/monitor support to automatically stop 
> idle services.  The Service Manager's start-by-reference mechanism is then 
> used to start the service if some job later needs the service, with the only 
> loss being the time needed to initialize the service.
> The mechanism should also enable the ping/monitor to re-enable the service's 
> persistent running state if it determines this is needed.
> The proposed mechanism for this second step is to allow the ping/monitor to 
> enable or disable the service's "autostart" flag.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to