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 2013/05/23 23:20:20 UTC

[jira] [Commented] (UIMA-2752) DuccJobSubmit option --process_failures_limit is ignored

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

Lou DeGenaro commented on UIMA-2752:
------------------------------------

I ran a simple test that shows this feature works...I'll need to look at the job you cite to understand what's different.

In my test, I submitted a job with --process_failures_limit 1 and waited until at least one JP had initialized.  I then killed one running JP at random and the job was terminated according to plan, since the process failures limit was reached.

On the Jobs page, I see Reason = ProcessFailure, and when I hover I see: health monitor detected job process failures limit reached: 1

For the process I killed, the State Agent = Failed and the Reason Agent = Croaked

                
> DuccJobSubmit option --process_failures_limit is ignored
> --------------------------------------------------------
>
>                 Key: UIMA-2752
>                 URL: https://issues.apache.org/jira/browse/UIMA-2752
>             Project: UIMA
>          Issue Type: Bug
>          Components: DUCC
>         Environment: When set to 2 the job was killed after 15 work-items failed.
> P7 job 1287 shows 5 failing JPs each with 3 errors.  The scaleout was 1 (e.g. all failed in the same thread 71) but since the failures were fast it produced 3 before the job was cancelled.  Since there was only 1 thread these extra failures should probably not have been considered collateral damage and retried.
> Is the limit work-item failures or process failures?
>            Reporter: Burn Lewis
>            Assignee: Lou DeGenaro
>            Priority: Minor
>             Fix For: 1.0-Ducc
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira