[
https://issues.apache.org/jira/browse/UIMA-5193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15749634#comment-15749634
]
Lou DeGenaro commented on UIMA-5193:
------------------------------------
move_ducc should insure that the current head node and the target (new head)
node are:
a) both in the same node pool, or
b) both not in any node pool.
NodeConfiguration.java - add new -m <node> flag to request the node pool for
the given node
ducc_util.py - add new get_nodepool(node) utility to invoke NodeConfiguration
class to fetch node pool for a given node
move_ducc - employ get_nodepool(node) for head and target nodes. if not
compatible complain and prevent move.
code is delivered.
> 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)
