[
https://issues.apache.org/jira/browse/UIMA-3602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lou DeGenaro resolved UIMA-3602.
--------------------------------
Resolution: Fixed
Fix Version/s: (was: future-DUCC)
2.0.0-Ducc
DUCC 2.0 employs JP pull model, so JD knows where work items are dispatched at
all times.
> DUCC Job Driver (JD) race between volunteering JPs and work item retry
> ----------------------------------------------------------------------
>
> Key: UIMA-3602
> URL: https://issues.apache.org/jira/browse/UIMA-3602
> Project: UIMA
> Issue Type: Bug
> Components: DUCC
> Affects Versions: 1.0.0-Ducc
> Reporter: Lou DeGenaro
> Assignee: Lou DeGenaro
> Priority: Minor
> Fix For: 2.0.0-Ducc
>
>
> As a Job winds down, the DUCC Orchestrator (OR) may voluntarily relinquish a
> Job Process (JP) while in close time proximity the Job Driver (JD) may retry
> a work item which gets dispatched to same.
> See org.apache.uima.ducc.orchestrator.StateManager deallocateIdleProcesses()
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
