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 2017/01/05 18:25:58 UTC
[jira] [Closed] (UIMA-5193) DUCC failover support (static)
[ https://issues.apache.org/jira/browse/UIMA-5193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lou DeGenaro closed UIMA-5193.
------------------------------
> 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)