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 2015/04/09 21:03:13 UTC

[jira] [Created] (UIMA-4337) Isolate DUCC Agent so that it is not dependent on common and transport

Jerry Cwiklik created UIMA-4337:
-----------------------------------

             Summary: Isolate DUCC Agent so that it is not dependent on common and transport
                 Key: UIMA-4337
                 URL: https://issues.apache.org/jira/browse/UIMA-4337
             Project: UIMA
          Issue Type: Improvement
          Components: DUCC
            Reporter: Jerry Cwiklik
            Assignee: Jerry Cwiklik
             Fix For: future-DUCC


Changes to common and transport require Agent restart. Since the restart means killing all running jobs (JDs, JPs and Services) such action can be expensive. 
The proposal is to find a way to remove Agent dependency on common and transport jars. Agent code should be isolated and self contained. This requires major refactoring with impact on other Ducc daemons. 
Currently an Agent publishes its inventory of processes using common classes included in transport jar. It also publishes metrics using classes from common jar. Those publications are consumed by RM, OR, and WS. The Agent uses common code to bootstrap and configure itself just like all of the Ducc daemons. 




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