Versions Compared

Old Version 12

changes.mady.by.user Sarabjeet Kaur

Saved on

compared with

New Version 13

changes.mady.by.user Sarabjeet Kaur

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • 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, 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 ENABLE_KM_HA property, and then set the value of the ENABLE_KM_HA property to 'Yesyes'. By default, this property is set to 'Nono', 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.

    image-20240124-145458.pngImage Added
Panel
panelIconIdatlassian-info
panelIcon:info:
bgColor#FFFAE6

Important

  • If Zookeeper goes down, then Kyvos Manager HA will not work till the time Zookeeper gets restored.

  • If Zookeeper is unavailable then any activities expected from non active Kyvos Manager instance will not work.

  • If Zookeeper is not available as HA then restore Zookeeper for proper working of Kyvos Manager HA.

  • In the absence of Zookeeper, all the existing Kyvos Manager instances will continue their last state i.e. active one will remain active and passive instance will continue to remain as passive.

  • If Kyvos Manager repository is inaccessible or down then Kyvos Manager or Kyvos Manager HA will not work. In this case, you need to perform Disaster Recovery.

  • If all BI server nodes go down due to scheduling and have Zookeeper deployed on them, Kyvos Manager HA will not work.

  • It is recommended to have multiple Zookeeper for proper working of Kyvos Manager HA. The cluster having single Zookeeper on Kyvos Manager node and Kyvos Manager node itself becomes down then passive services of Kyvos Manager cannot promote themselves as Active.

...