[
https://issues.apache.org/jira/browse/UIMA-3577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13904006#comment-13904006
]
Lou DeGenaro commented on UIMA-3577:
------------------------------------
JobDriver class changes:
1. Make ThreadPool creation into a reusable method
2. ThreadPool creator shutdown's previous pool (if any) then creates new one
3. Do not pre-start all core threads (not 100% sure this is necessary, but will
become moot if/when asynchronous UIMA-AS client is employed)
4. Adjust missingCallbackReaper() to account for CasSource empty CR and
retryable delayed CAS's
5. Create requeue() to put CAS's onto the delayed retry queue
6. Refactor process() method code to create queue() method
7. Refactor process() method to employ requeue(), queue() and
missingCallbackReaper()
8. Adjust queueCASes() to account for CasSource CR and retryable delayed CAS's
9. Adjust interrupter() to account for retryable delayed CASes
10. Add method delayedRetry to manage newly declared lost work items
11. ended() and exception() to record warning and toss unexpected CAS's
11. lost() method to perform accounting and place work items on delayed retry
queue
> DUCC job driver (JD) should auto-retry lost work items
> ------------------------------------------------------
>
> Key: UIMA-3577
> URL: https://issues.apache.org/jira/browse/UIMA-3577
> Project: UIMA
> Issue Type: Improvement
> Components: DUCC
> Environment: Currently work item is "lost" after 5 minutes and
> callback #2 has not triggered.
> Lost work items are presently not auto-retried.
> Reporter: Lou DeGenaro
> Assignee: Lou DeGenaro
> Fix For: 2.0-Ducc
>
>
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
