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 2014/06/19 14:25:24 UTC

[jira] [Updated] (UIMA-3448) DUCC orchestrator (OR) and job driver (JD) should not retry forever work items that appear on failing JPs

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

Lou DeGenaro updated UIMA-3448:
-------------------------------

    Summary: DUCC orchestrator (OR) and job driver (JD) should not retry forever work items that appear on failing JPs  (was: DUCC orchestrtor (OR) and job driver (JD) should not retry forever work items that appear on failing JPs)

> DUCC orchestrator (OR) and job driver (JD) should not retry forever work items that appear on failing JPs
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: UIMA-3448
>                 URL: https://issues.apache.org/jira/browse/UIMA-3448
>             Project: UIMA
>          Issue Type: Bug
>          Components: DUCC
>            Reporter: Lou DeGenaro
>            Assignee: Lou DeGenaro
>             Fix For: future-DUCC
>
>
> One or more work items may cause a Job Process (JP) to crash.  The work items should be tracked and given-up on after some number of JP crashes.  And/or there should be some limit to the number of JP crashes for the Job before it is auto-terminated for cause.



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