Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

Applies to: (tick) Kyvos Enterprise  (error) Kyvos Cloud (SaaS on AWS) (error) Kyvos AWS Marketplace

(error) Kyvos Azure Marketplace   (error) Kyvos GCP Marketplace (error) Kyvos Single Node Installation (Kyvos SNI)


This section outlines the steps to be taken after completing the upgrade process.

Post-upgrade steps to manually configure Heap memory

Note

From Kyvos 2023.5 onwards, Heap, Off-heap, and other required memory on Query Engines are automatically configured if memory mode is set to Auto mode.  

For a manual memory mode, you must perform the following post-deployment steps. 

  • Open the Kyvos Java options page in Kyvos Manager and Navigate to the Query Engine section. 

  • If Configure Heap memory for Query Engine is set as Auto, no need is required. 

  • If Configure Heap memory for Query Engine is set as Manual, reduce Off-Heap memory by 10 GB. 
    For Example, Suppose the total machine memory is 128 GB, whereas 45 GB is assigned to Heap, and 66 GB is assigned to Off-Heap. In that case, you need to set Heap as 45 GB and Off-Heap as 56 GB so Kyvos can use the remaining 10 GB internally for the new data store-based architecture. 

Post-upgrade steps for Azure to update AzCopy version

Note

From Kyvos 2024.3 onwards, the AzCopy version is upgraded from 10.16 to 10.25.

To upgrade the AzCopy version, perform the following steps on each Kyvos node (BI Server, Query Engine, Kyvos Manager, Web Portal).

  1. SSH to Kyvos node.

  2. Navigate to the cd /tmp directory by executing the following command.

  3. Upload the UpdateAzcopy.sh script (provided in the AzureInstallationFiles folder) and provide the execute permission by running the chmod 755 UpdateAzcopy.sh command.

  4. Run the ./UpdateAzcopy.sh command. You can also verify the version by running the azcopy --version command.

Migrating Storage account TLS version from 1.0 to TLS 1.2

From Kyvos 2024.1 onwards, for fresh deployments on Azure, the minimum TLS version value must be 1.2. For existing environments, you need to perform the following post-deployment steps to migrate from TLS 1.0 and 1.1 to TLS 1.2.

Note

As of November 1, 2024, Azure Storage will no longer support TLS 1.0 and 1.1. It is essential to migrate to TLS 1.2 before this date.

  1. Go to your Azure Storage account.

  2. On the Home page, click Overview, and then click the Properties tab.

  3. In the Security section, click Minimum TLS version and update it to 1.2 and then click Save.

  • No labels