You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@uima.apache.org by "Lou DeGenaro (JIRA)" <de...@uima.apache.org> on 2016/04/20 21:20:25 UTC

[jira] [Updated] (UIMA-4903) DUCC Orchestrator (OR) Health Monitor fails to detect too many Job Process failures

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

Lou DeGenaro updated UIMA-4903:
-------------------------------
    Summary: DUCC Orchestrator (OR) Health Monitor fails to detect too many Job Process failures  (was: DUCC Orchestrator (OR) Health Monitor should remove isInitialized constraint when checking for excessive Job Process (JP) failures)

> DUCC Orchestrator (OR) Health Monitor fails to detect too many Job Process failures
> -----------------------------------------------------------------------------------
>
>                 Key: UIMA-4903
>                 URL: https://issues.apache.org/jira/browse/UIMA-4903
>             Project: UIMA
>          Issue Type: Improvement
>          Components: DUCC
>            Reporter: Lou DeGenaro
>            Assignee: Lou DeGenaro
>             Fix For: 2.1.0-Ducc
>
>
> To assure a failing Job does not mistakenly live forever, the OR health monitor should not use initialization completed as a criteria for enforcing the too many JP failures limit.



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