[
https://issues.apache.org/jira/browse/UIMA-2944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13669603#comment-13669603
]
Lou DeGenaro edited comment on UIMA-2944 at 5/29/13 7:40 PM:
-------------------------------------------------------------
JD did not bother to determine current Limbo status prior to report
publication. This sometimes resulted in falsely high counts of items in Limbo,
since we then relied upon the "occasional" CasSource getNext() method
invocation which itself does lazy reclamation.
was (Author: lou.degenaro):
JD did not bother to determine current Limbo status prior to status report
publication.
> DUCC Job Driver (JD) reports state Limbo status
> -----------------------------------------------
>
> Key: UIMA-2944
> URL: https://issues.apache.org/jira/browse/UIMA-2944
> Project: UIMA
> Issue Type: Improvement
> Components: DUCC
> Reporter: Lou DeGenaro
> Assignee: Lou DeGenaro
> Priority: Minor
> Fix For: 1.0-Ducc
>
>
> All the work items with status retry are counted as limbo. Maybe this:
> Id: 47069 Workitems: 622 Done: 206 Error: 13 Dispatch: 75 Unassigned: 1
> Limbo: 40
> Should become this:
> Id: 47069 Workitems: 622 Done: 206 Error: 13 Dispatch: 75 RetryQueue: 40
> Unassigned: 1 Limbo: 0
--
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
