uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lou DeGenaro (JIRA)" <...@uima.apache.org>
Subject [jira] [Work started] (UIMA-5193) DUCC failover support (static)
Date Thu, 01 Dec 2016 15:29:58 GMT

     [ https://issues.apache.org/jira/browse/UIMA-5193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Work on UIMA-5193 started by Lou DeGenaro.
> 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

View raw message