[
https://issues.apache.org/jira/browse/UIMA-6037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16857797#comment-16857797
]
Lou DeGenaro edited comment on UIMA-6037 at 6/6/19 7:39 PM:
------------------------------------------------------------
Design 1 - distributed autostart
In this design, each agent node independently runs autostart. This requires
each agent to "call home" to ducc master node to request ducc_rcync push
followed by local invocation ducc.py start. To minimize security risk, agent
nodes should only have broker (and not DB pw). The autostart would start a
bootstrap java agent to employ head node broker connection to request
ducc_rsync...from ducc-mon?
Design 2 - centralized autostart
In this design, ducc-mon employs an autostart thread that periodically checks
the status of agent nodes. For any found down that should be up, ducc-mon
autostart thread (conditional on shared filesystem absence) performs
ducc_rsync, followed by start_ducc. Advantage here is that no special boostrap
agent (java code with broker connection) need be coded or launched. However, a
dynamically added node would have to signal ducc-mon of its genesis, perhaps by
simple http request "register-me".
was (Author: lou.degenaro):
Design 1 - distributed autostart
In this design, each agent node independently runs autostart. This requires
each agent to "call home" to ducc master node to request ducc_rcync push
followed by local invocation ducc.py start. To minimize security risk, agent
nodes should only have broker (and not DB pw). The autostart would start a
bootstrap java agent to employ head node broker connection to request
ducc_rsync...from ducc-mon?
Design 2 - centralized autostart
In this design, ducc-mon employs an autostart thread that periodically checks
the status of agent nodes. For any found down that should be up, ducc-mon
autostart thread (conditional on shared filesystem absence) performs
ducc_rsync, followed by start_ducc. Advantage here is that no special boostrap
agent need be coded or launched. Also, a dynamically added node would have to
signal ducc-mon of its genesis, perhaps by simple http request "register-me".
> agent autostart should rsync its local ducc_runtime tree
> --------------------------------------------------------
>
> Key: UIMA-6037
> URL: https://issues.apache.org/jira/browse/UIMA-6037
> Project: UIMA
> Issue Type: Improvement
> Components: DUCC
> Affects Versions: 3.0.0-Ducc
> Reporter: Eddie Epstein
> Assignee: Lou DeGenaro
> Priority: Major
> Fix For: 3.0.1-Ducc
>
>
> If a DUCC worker node is instantiated from a VM image its local image of
> ducc_runtime may be out of date relative to the current system.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
