[UIMA-3390] DUCC job driver (JD) should be more cautious about queuing work items in the presence of failed ones

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.0.0-Ducc
• Component/s: DUCC
• Assignee: Lou DeGenaro
• Reporter: Lou DeGenaro
• Created: 29/Oct/13 14:41
• Updated: 17/Mar/15 17:59
• Resolved: 17/Mar/15 17:59

Description

I think I understand this problem. Bhavani's job 96348 happens to have excellent characteristics with 1 JP and 1 thread.

It seems that one of her work items causes the JP to explode (Croaked). The work items fails. The JD marks the work item as Error. So far so good. The JD proceeds to queue the next work item for processing not realizing that the lone JP has vanished. This is a mistake. Correctly, a new JP is allocated by the Scheduler, and not until its initialization is completed does the longtime queued work item get picked up.

The JD should probably be more cautious about queuing work items in the presence of failed ones.