Applies to: 
Kyvos Enterprise Kyvos Cloud (Managed Services Kyvos Cloud (SaaS on AWS) Kyvos Azure AWS Marketplace
Kyvos AWS Azure Marketplace Kyvos Kyvos GCP Marketplace Kyvos Single Node Installation (Kyvos SNI) Kyvos Free (Limited offering for AWS)
...
Kyvos is designed to handle the high availability of components as well as being capable of balancing access to the system. The Kyvos BI Server is highly available and active/active. There is no downtime switching BI Servers, allowing Kyvos to scale horizontally without a single point of failure. Any role can be assumed by any engine in the cluster.
The Kyvos BI Server cluster is built on a a Floating Master approach. Multiple instances of the Kyvos engine form a cluster governed by a coordination master. The coordination master is highly available. If there is a failure, its role is assumed by other nodes in the cluster without downtime. Requests are distributed to the appropriate Kyvos BI Server using a round-robin algorithm.
The Kyvos Postgres server generally resides on the BI Server node. For high availability, it can be configured to have separate nodes for Active and Standby instances. The Postgres nodes have a live syncing mechanism with automatic failover activated. In case the Active server goes down, the Standby server comes up after the predefined wait interval. There is no data loss and zero failure.
High availability configuration from Kyvos Manager
To configure high availability for the Kyvos Web Portal and Postgres Server from the Kyvos Manager, perform the following steps.
On the navigation pane, click Kyvos and Ecosystem > Node and Services.
The Node and Services page is displayed.
...
To configure high availability for the Web portal, select the Web Portal option from the Services list and provide details as :
Info title Info The Node and Service mapping page shows the number of instances configured in your cluster and the number of instances that are allowed by your license.
Parameter | Description |
|---|---|
Enable Session Management | Select to enable Tomcat-based session management. Do not select this for cloud clusters with a load balancer configured for Web Portal HA. |
Multicast Address | Specify the multicast IP address that will be used for multi-casting messages to all web portal IP/Hostname. It is a logical identifier for a group of hosts in a computer network that is available for processing. Read more |
Multicast Port | Enter is the multicast port to be used for sending multicast messages. |
Receiver Port | Enter the port that will be used as the receiver port |
Virtual IP/Hostname | Enter the virtual IP/Hostname in the protocol://host:port format to access the Kyvos Web Portal when the Web Portal is configured with high availability mode. It is the single IP/Hostname that will be used to access the Kyvos Web Portal, regardless of the IP/Hostname on which the Web Portal is actually running. NOTE: If protocol and port are not specified, those will be picked from the Web Portal URL. |
You can also configure high availability for the Postgres server on the Services High Availability page. See the Configuring high availability section for more details.