[jira] [Updated] (UIMA-2689) DUCC webserver (WS) auto-cancel feature should not be enabled for "shadows"

["Jerry Cwiklik (JIRA)" <de...@uima.apache.org>]

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

Jerry Cwiklik updated UIMA-2689:
--------------------------------

    Fix Version/s: 1.0-Ducc

> DUCC webserver (WS) auto-cancel feature should not be enabled for "shadows"
> ---------------------------------------------------------------------------
>
>                 Key: UIMA-2689
>                 URL: https://issues.apache.org/jira/browse/UIMA-2689
>             Project: UIMA
>          Issue Type: Bug
>          Components: DUCC
>            Reporter: Lou DeGenaro
>            Assignee: Lou DeGenaro
>            Priority: Minor
>             Fix For: 1.0-Ducc
>
>
> The auto-cancel feature is enabled when --cancel_on_interrupt flag is specified at submit time.  When this flag is specified, the WS expects to receive regular pings from the submitter, which are automatically supplied by the associated monitor.  If pings are absent for too long (config'd in ducc.properties via ducc.ws.job.automatic.cancel.minutes) the WS proceeds to cancel the job.
> It is possible to run multiple WS instances (aka "shadows").  Since only one is ping'd, the other(s) will detect a ping timeout and incorrectly cancel the job.
> The solution is to have only the "primary" WS as the monitor+canceler.  This is determined by matching the specification in ducc.properties for WS host:port with that of the actual host:port of the WS.  Only if these match will the auto-cancel code be enabled in the WS.
> To bypass this problem until fix is delivered, run only a single WS.



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