You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Jerry Cwiklik (JIRA)" <de...@uima.apache.org> on 2013/12/20 19:00:30 UTC

[jira] [Closed] (UIMA-2591) Provide ability to cancel an individual DUCC Job Process

     [ https://issues.apache.org/jira/browse/UIMA-2591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jerry Cwiklik closed UIMA-2591.
-------------------------------

    Resolution: Fixed

> Provide ability to cancel an individual DUCC Job Process 
> ---------------------------------------------------------
>
>                 Key: UIMA-2591
>                 URL: https://issues.apache.org/jira/browse/UIMA-2591
>             Project: UIMA
>          Issue Type: New Feature
>          Components: DUCC
>            Reporter: Lou DeGenaro
>            Assignee: Lou DeGenaro
>            Priority: Minor
>             Fix For: 1.0-Ducc
>
>
> Presently, a DUCC Job may be unable to make forward progress (including termination) due to a Job Process [JP] that was dispatched to an Agent that is no longer communicating.  The only way to rescue this Job (without recylcing DUCC itself) is to have the Agent start reporting again, which may not be feasible (for example a HW problem has caused the system to crash and precludes system boot and therefore Agent from running).
> Provided here is the ability to cancel a particular JP, thus making any and all incomplete Work Items previously dispatched to that JP re-deployable elsewhere.
> The DUCC CLI is enhanced to provide the --dpid flag to the job cancel command.
> Note well:  if there is any possibility that the target JP is active but the Agent is not, then this flag should not be used, so as to avoid the possibility of the same Work Item being processed by two JPs simultaneously.



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)