[
https://issues.apache.org/jira/browse/UIMA-2696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13587323#comment-13587323
]
Lou DeGenaro commented on UIMA-2696:
------------------------------------
The job (1215) has reach the initialization threshold of at least one JP
finished initialization. Very nice. But it seems that some subsequent JPs
failed to initialized (eg Croaked) and were counted as Run fails. It seems
that these should be counted as Init fails.
For example in JP 50 (PID 22674) log we see:
Service:ducc.jd.queue.1215 Initialized. Ready To Process Messages From
Queue:ducc.jd.queue.1215
But we don't get that far in, say, JP 65 (PID 28540) log.
Might be something "funny" about Croaking, dunno...
Also, I don't think exceeding the max init failures will kill the job, but
rather will "cap" it to prevent further expansion (ie - resource allocation)
attempts.
> Initialization errors falsely reported as Run errors
> ----------------------------------------------------
>
> Key: UIMA-2696
> URL: https://issues.apache.org/jira/browse/UIMA-2696
> Project: UIMA
> Issue Type: Bug
> Components: DUCC
> Reporter: Burn Lewis
> Assignee: Lou DeGenaro
> Priority: Minor
>
> Job 1215 was killed because it had 20 Init errors that were falsely reported
> as Run errors.
--
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
