[
https://issues.apache.org/jira/browse/UIMA-2591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lou DeGenaro updated UIMA-2591:
-------------------------------
Description:
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.
was:
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
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.
> 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
> Reporter: Lou DeGenaro
> Priority: Minor
>
> 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 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
