Kyvos Manager, which is a cluster management tool for Kyvos, currently supports configuring multiple instances of services like BI Server, Query Engine, Kyvos Web Portal, and Postgres that work in high availability mode. Kyvos services can operate normally even in the absence of the Kyvos Manager. However, certain features such as Services HA, configuring properties, Postgres High Availability for bundled Postgres, Hadoop connection Configuration & Lib Sync from Compute cluster or DFS, regardless of SSH or non-SSH mode, are dependent on Kyvos Manager. If any of these features are required at any time, an instance of Kyvos Manager must be running for Kyvos to work properlycorrectly. Therefore, from Kyvos 2024.1 onwards, Kyvos Manager supports high availability in case of instance failure, and immediately, another instance will be active to serve the requirement.
...
Adding Kyvos Manager (KM) instances is supported only on nodes with Kyvos Web Portal , as a cost optimization strategy. Thus, Kyvos Manager HA requires Web Portal HA as a precondition.
For Kyvos Manager HA, the Zookeeper must be up and running.
Each node in a cloud cluster must have the respective CLI command (aws, azcopy, gsutil), while on-premises, it must have the HDFS command and access to HDFS.
For cloud environments, a Load balancer must be configured in the cluster.
Irrespective of the type of repository used for Kyvos Manager, the repository must be accessible from all Kyvos Manager nodes.
All newly added instances of Kyvos Manager must have the same permissions (IAM Role, Managed Identity) and network access permissions (Security Group, Local Firewall) as the Kyvos Manager node.
To enable the Kyvos Manager High Availability mode, you need to navigate to the Kyvos Manager Settings > Kyvos Manager Properties.On the Kyvos Manager Properties page, search for the ENABLE_KM_HA property, and then set the value of the ENABLE_KM_HA property to 'yes'‘yes.’ By default, this property is set to 'no'‘no,’ which means that the Kyvos Manager HA mode is disabled and will not be displayed on the Kyvos Manager Dashboard. Therefore, if you want to make the Kyvos Manager HA available, you need to update the value of this property to 'yes'‘yes.’ After enabling the Kyvos Manager High Availability through this property, Kyvos Manager will restart. After restarting Kyvos Manager, the Kyvos Manager Disaster Recovery script must be pushed, as shown below.
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
Important
|
| Tip |
|---|
Tip In cloud-based environments, where a load balancer is used, all requests will only go to the active Kyvos Manager only. When a passive Kyvos Manager node URL is accessed, you will be redirected to the load balancer URL or Active Kyvos Manager node URL (when the load balancer is not configured). |
...
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
Note
|
...
You can view the detailed Kyvos Manager instance properties for both Active and Passive mode. You can also modify the alias name of the node at any time.
...
In the Kyvos Manager Nodes section, click the circle (Red/Green), and the Action menu (…) appears.
Click Properties. The Properties dialog is displayed.
On the Properties dialog, you can specify an Alias name to for a node, which can be easily modified later.
The Alias name will be displayed in the Alias column.
...
You can start, restart, or stop a single Kyvos Manager Service for the service which that is in a Passive mode, as shown in the image below image.
...
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
Note From this section, you cannot start, stop, or restart the Kyvos Manager Service that is in Active mode. |
Click Start Kyvos Manager Service, and the following dialog is displayed.
Provide your Kyvos Manager password and then click Save. The Kyvos Manager Service will start.
...
You can start, restart, or stop all Kyvos Manager Services for the services which are in a Passive mode, as shown in the image below.
...
Click Start Kyvos Manager Service, and the following dialog is displayed.
Provide your Kyvos Manager password and then click Save. The Kyvos Manager Service will start.
...
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
Note The Kyvos Manager service in Active mode is always disabled since only passive services can be started, stopped, or restarted. |
Restart Active Kyvos Manager Instance
You can also restart the active Kyvos Manager instance. To do this, click the Action Menu appears at the right of the page, and then click Restart Active Kyvos Manager Instance.
...
To restart the single Active Kyvos Manager Node, click the Actions (…) next to Kyvos Manager and then click Restart Active Kyvos Manager Instance, as shown in the image below image.
...
The following dialog is displayed.
...
If Kyvos Manager HA is not configured:
Default The default existing single Kyvos Manager node will continue to work as an Active node.
On Kyvos Manager Dashboard, no rows related to where Kyvos Manager instances are running will be displayed.
On the Migrate role page, no option to add or remove the Kyvos Manager instance will be available.
Snapshots will not be pushed in ON PREM deployments during Upgrade, Rollback, Patch in on-prem deployments.
Kyvos Manager will not connect to Zookeeper.
Start, stop, or restart the Kyvos Manager server, which will continue to appear as it is like was earlier.
On When changing the Kyvos Manager property, only the Kyvos Manager configuration bundle snapshot was pushed. However, if the Kyvos Manager HA property is enabled, then all the Kyvos Manager snapshot bundles will be pushed.
Schema for Kyvos Manager HA instances will be created even if Kyvos Manager HA is not enabled.
Known limitation
As this is a an initial version of Kyvos Manager HA for the Kyvos 2024.1 release, you will encounter the following limitations:
Download logs of passive Kyvos Manager instances are not supported.
Make a passive Kyvos Manager instance as an active instance from Kyvos Manager is not supported.
Configuring Kyvos Manager HA during a cluster deployment (irrespective of whether automated or wizard-based) is not supported.