...
Kyvos Azure Marketplace Kyvos GCP Marketplace Kyvos Single Node Installation (Kyvos SNI)
...
This section defines the post-upgrade steps for:
Post-upgrade steps to manually configure Heap memory
| Anchor | ||||
|---|---|---|---|---|
|
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
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. |
...
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
| Anchor | ||||
|---|---|---|---|---|
|
Azure Functions
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
Note Applicable ONLY when you have upgraded Azure Cloud-based cluster where functions were deployed for supporting scheduling feature. |
...
On the Kyvos Manager portal, navigate to the Properties page. In the kyvosclient.properties file, update the CLUSTER_STARTUP_URL and SERVER_STATUS_CHECK_URL properties with URL available in old functions created before the upgrade.
Logon to your Azure portal, and navigate to <Container> / user / <work directory> / setup / cloud_conf. Download the cluster.properties file, update the FUNCTION_NAME property to provide the previous function name that was created before the upgrade, and upload the updated file.
Restart the BI Server.
Migrating Storage account TLS version from 1.0 to TLS 1.2
| Anchor | ||||
|---|---|---|---|---|
|
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.
...