You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Burn Lewis (JIRA)" <de...@uima.apache.org> on 2017/04/03 14:57:42 UTC

[jira] [Commented] (UIMA-5390) DUCC may restart failing custom services forever

    [ https://issues.apache.org/jira/browse/UIMA-5390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15953622#comment-15953622 ] 

Burn Lewis commented on UIMA-5390:
----------------------------------

Could make the SM put custom services in an init phase until the pinger reports that an instance has initialized (i.e. registered.). The custom pinger could hang and poll the registry frequently and only return when the first instance registered.  This should let the SM recognize the transition to running fairly quickly. 

> DUCC may restart failing custom services forever
> ------------------------------------------------
>
>                 Key: UIMA-5390
>                 URL: https://issues.apache.org/jira/browse/UIMA-5390
>             Project: UIMA
>          Issue Type: Bug
>          Components: DUCC
>            Reporter: Burn Lewis
>            Priority: Minor
>             Fix For: future-DUCC
>
>
> Since custom services have no initialization phase all init errors are counted as run errors, but before the threshold is reached the error count may be reset.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)