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 2018/07/24 17:38:00 UTC
[jira] [Updated] (UIMA-5843) UIMA-DUCC: pull service should support
error window
[ https://issues.apache.org/jira/browse/UIMA-5843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jerry Cwiklik updated UIMA-5843:
--------------------------------
Description:
Currently, a pull service terminates on the 1st process error. In some cases, this might not be desirable. Add an error handler which supports an error window. It should be based on max number of errors (ME) in a given window(W). Examples:
(ME,W)
(0,0) - never terminate on errors
(1,1) - terminate on first error
(2, 5) - terminate on second error in a window of 5 tasks
The default will be (1,1).
For jobs, the Orchestrator will add two new -D's to JP command line if a job spec defines a custom error window
ducc.deploy.service.error.threshold=ME
ducc.deploy.service.error.window=W
An application with an embedded PullService can change the default error window by calling a new method of IServiceProcessor
public void setErrorHandlerWindow(int maxErrors, int windowSize);
Changes are needed in the job spec to support optional error window properties (max errors and window size). Also, the OR needs to change to add -Ds as mentioned above. Duccbook needs an update as well to document new job properties.
was:
Currently, a pull service terminates on the 1st process error. In some cases, this might not be desirable. Add an error handler which supports an error window. It should be based on max number of errors (ME) in a given window(W). Examples:
(ME,W)
(0,0) - never terminate on errors
(1,1) - terminate on first error
(2, 5) - terminate on second error in a window of 5 tasks
The default will be (1,1).
For jobs, the Orchestrator will add two new -D's to JP command line if a job spec defines a custom error window
ducc.deploy.service.error.threshold=ME
ducc.deploy.service.error.window=W
An application with an embedded PullService can change the default error window by calling a new method of IServiceProcessor
public void setErrorHandlerWindow(int maxErrors, int windowSize);
> UIMA-DUCC: pull service should support error window
> ---------------------------------------------------
>
> Key: UIMA-5843
> URL: https://issues.apache.org/jira/browse/UIMA-5843
> Project: UIMA
> Issue Type: Improvement
> Components: DUCC
> Reporter: Jerry Cwiklik
> Assignee: Jerry Cwiklik
> Priority: Major
> Fix For: 2.2.3-Ducc
>
>
> Currently, a pull service terminates on the 1st process error. In some cases, this might not be desirable. Add an error handler which supports an error window. It should be based on max number of errors (ME) in a given window(W). Examples:
> (ME,W)
> (0,0) - never terminate on errors
> (1,1) - terminate on first error
> (2, 5) - terminate on second error in a window of 5 tasks
> The default will be (1,1).
> For jobs, the Orchestrator will add two new -D's to JP command line if a job spec defines a custom error window
> ducc.deploy.service.error.threshold=ME
> ducc.deploy.service.error.window=W
> An application with an embedded PullService can change the default error window by calling a new method of IServiceProcessor
> public void setErrorHandlerWindow(int maxErrors, int windowSize);
> Changes are needed in the job spec to support optional error window properties (max errors and window size). Also, the OR needs to change to add -Ds as mentioned above. Duccbook needs an update as well to document new job properties.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)