[jira] [Updated] (UIMA-4321) DUCC should not retry JPs forever when the JP framework fails

["Jerry Cwiklik (JIRA)" <de...@uima.apache.org>]

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

Jerry Cwiklik updated UIMA-4321:
--------------------------------
    Affects Version/s:     (was: 2.0.0-Ducc)
        Fix Version/s: 2.0.0-Ducc

> DUCC should not retry JPs forever when the JP framework fails
> -------------------------------------------------------------
>
>                 Key: UIMA-4321
>                 URL: https://issues.apache.org/jira/browse/UIMA-4321
>             Project: UIMA
>          Issue Type: Bug
>          Components: DUCC
>            Reporter: Burn Lewis
>            Assignee: Jerry Cwiklik
>            Priority: Blocker
>             Fix For: 2.0.0-Ducc
>
>
> Job 235131 had a large string of JPs fail (when the JD OOM'd) with:
> HttpWorkerThread.run() I/O exception (org.apache.commons.httpclient.NoHttpResponseException) caught when processing request: The server 192.168.3.77 failed to respond
> For the short-term we should count this as a Croak (i.e. an unexpected termination that DUCC didn't request), even though it is not caused by user error, so that the users's process_failures_limit can eventually end the job.
> Perhaps we need a "framework_failures_limit" in ducc.properties for errors caught in the ducc-side JP code as opposed to errors caught in user code.



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