<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>High Availability on Kinetica Docs</title><link>/7.1/ha/</link><description>Recent content in High Availability on Kinetica Docs</description><generator>Hugo -- gohugo.io</generator><language>en</language><atom:link href="/7.1/ha/index.xml" rel="self" type="application/rss+xml"/><item><title>High Availability Architecture</title><link>/7.1/ha/ha_architecture/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/7.1/ha/ha_architecture/</guid><description>Failover Modes Failure and Recovery High Availability Processing Operation Handling Synchronous Operations Asynchronous Operations Queries Eventual Consistency Data Synchronization Recovery The Kinetica HA eliminates the single point of failure in a standard Kinetica cluster and provides recovery from failure. It is implemented within the cluster to utilize multiple replicas of data and provides an eventually consistent data store, by default. Through modification of the configuration, immediate consistency can also be achieved, though at a performance cost.</description></item><item><title>High Availability Configuration &amp; Management</title><link>/7.1/ha/ha_configuration/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/7.1/ha/ha_configuration/</guid><description>Pre-requisites Configuration Enable HA Config HA APIs Connectors External Data Management Pre-requisites An HA installation requires the following components:
Two or more clusters with matching Kinetica installations managed by KAgent
Note
If the clusters are not managed, KAgent should be installed and then the clusters should be added to it.
Two nodes (across the clusters) have RabbitMQ installed
etcd
The KAgent UI
Configuration Enable HA HA is enabled on a ring using the KAgent UI.</description></item></channel></rss>