You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Jim Challenger (JIRA)" <de...@uima.apache.org> on 2015/03/26 20:58:54 UTC

[jira] [Closed] (UIMA-4309) DUCC: SM track time of last good ping and last process Running

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

Jim Challenger closed UIMA-4309.
--------------------------------
    Resolution: Fixed

> DUCC: SM track time of last good ping and last process Running
> --------------------------------------------------------------
>
>                 Key: UIMA-4309
>                 URL: https://issues.apache.org/jira/browse/UIMA-4309
>             Project: UIMA
>          Issue Type: Improvement
>          Components: DUCC
>    Affects Versions: 1.1.0-Ducc
>            Reporter: Jim Challenger
>            Assignee: Jim Challenger
>             Fix For: 2.0.0-Ducc
>
>
> Have SM track date of last good ping and last time at least one of the instances is in state Running.
> Use cases: 
> Sometimes services will be registered and started with bad pingers, and then used without declaring dependencies.  This is an acceptable use case but if the pinger isn't working, it looks like the service is broken.  If we can tell at a glance there is at least one Running process we can better assess if the service is viable.
> Similarly, if the system glitches and causes service processes to die and the service to become Disabled, we can look at the last viable ping date and automate restarting services that were known to have been recently working.



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