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 2015/03/25 14:58:53 UTC

[jira] [Commented] (UIMA-4307) DUCC Job Driver (JD) must consider current Job state when evalutating initialization errors

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

Lou DeGenaro commented on UIMA-4307:
------------------------------------

Code is delivered.

> DUCC Job Driver (JD) must consider current Job state when evalutating initialization errors
> -------------------------------------------------------------------------------------------
>
>                 Key: UIMA-4307
>                 URL: https://issues.apache.org/jira/browse/UIMA-4307
>             Project: UIMA
>          Issue Type: Bug
>          Components: DUCC
>    Affects Versions: 2.0.0-Ducc
>            Reporter: Lou DeGenaro
>            Assignee: Lou DeGenaro
>            Priority: Minor
>
> Jobs that are already initialized are exempt from being killed when the initialization error limit threshold is met.  Instead, these jobs should be prevented from further expansion.
> The 2.0 JD fails to consider the Job's current state (e.g. Initializing vs. Active) when evaluating initialization errors, and thus it incorrectly kills Active Jobs that have crossed the initialization error threshold.



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