[
https://issues.apache.org/jira/browse/UIMA-5193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15725821#comment-15725821
]
Lou DeGenaro commented on UIMA-5193:
------------------------------------
bash-4.1$ ./ducc_runtime/admin/move_ducc --help
Usage: move_ducc [options]
Options:
-h, --help show this help message and exit
-d, --debug display debugging messages
-o, --offline indicate current DUCC head node is offline, Note: USE THIS
OPTION WITH EXTREME CAUTION else risk corrupting database
-q, --quiet do not display informational messages
Run this command on the host which will become the new DUCC head node.
Prerequisites:
1. the current ducc.head node in site.ducc.properties is up
2. the head daemons (broker, database, or, pm, rm, sm, ws) on the ducc.head
node are down (e.g. stop_ducc -c head)
Operation:
To the extent possible, the cluster will be checked to see if it is safe to
edit the site.ducc.properties file, and if so then a backup of the original
file is made then the requisite changes are made to realize the head node move.
> DUCC failover support (static)
> ------------------------------
>
> Key: UIMA-5193
> URL: https://issues.apache.org/jira/browse/UIMA-5193
> Project: UIMA
> Issue Type: Improvement
> Components: DUCC
> Reporter: Lou DeGenaro
> Assignee: Lou DeGenaro
> Fix For: 2.2.0-Ducc
>
>
> DUCC should provide the capability to move the head node, comprising the
> broker, database, Orchestrator, PM, RM, SM, and WS, and have the agents
> seamlessly switch over w/o service disruption.
> ---
> In this "static" failover implementation the agents are pre-configured with a
> list of potential head nodes. Introduced into the ducc.properties file is
> the key ducc.head.failover whose value is a comma separated list of failover
> nodes:
> ducc.head.failover = node1, node2, node3...
> The agents at boot time are configured for broker failover to this set of
> nodes.
> If ducc.head.failover is not specified, then the failover functionality is
> simply not supported for the installation (e.g. no seamless transition of
> running agents to an alternate broker head node).
> If ducc.head.failover is specified, then the node specified for ducc.head
> must appear in this list.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
