You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@uima.apache.org by "Lou DeGenaro (JIRA)" <de...@uima.apache.org> on 2015/04/27 15:56:38 UTC

[jira] [Updated] (UIMA-4361) DUCC Job Driver (JD) should only recieve pertinent info from Orchestrator (OR)

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

Lou DeGenaro updated UIMA-4361:
-------------------------------
    Fix Version/s: 2.0.0-Ducc

> DUCC Job Driver (JD) should only recieve pertinent info from Orchestrator (OR) 
> -------------------------------------------------------------------------------
>
>                 Key: UIMA-4361
>                 URL: https://issues.apache.org/jira/browse/UIMA-4361
>             Project: UIMA
>          Issue Type: Improvement
>          Components: DUCC
>    Affects Versions: 2.0.0-Ducc
>            Reporter: Lou DeGenaro
>            Assignee: Lou DeGenaro
>             Fix For: 2.0.0-Ducc
>
>
> OR publications can be large.  The JD only cares about its own Job, so all the rest is wasted bandwidth and memory.
> CLI and OR already communicate directly using HTTP.  JD will now use HTTP to publish its regular Status Reports and in return receive up-to-date Job information (e.g. new and gone JPs).
> OR --hot start should continue to work for already running Jobs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)