Applies to: 
Kyvos Enterprise Kyvos Cloud (SaaS on AWS) Kyvos AWS Marketplace
...
When the cluster usage duration is not fixed, you must use load-based scaling. This type of scaling allows you to set rules to automatically scale up or scale down the query engines based on usage patterns. By managing cluster scaling, you can enhance the utilization of your cloud cluster and save on compute costs. Additionally, you can set rules to automatically shut down or start the BI Servers and Query Engines to optimize resource utilization further.
To implement a scale-down rule, you can configure a setting to automatically reduce the capacity of your Query Engines when the cluster is under usage. Additionally, you can set a rule to automatically shut down the Query Engines and BI Servers if the cluster is not in use for a specified period. Similarly, for a scale-up rule, you can set a rule to automatically start the BI Servers and Query Engines with the required capacity when the cluster utilization exceeds over a defined period.
The Kyvos 2024.2 release comes with enhanced Load-based scaling.
Scaling rules are implemented based on the CPU load and memory usage of the Query Engine instances. System resources will be monitored for all BI Servers and Query Engines every 30 seconds, and Query Engines’ scaling will be performed based on this data.
To set a load-based scheduling, from the Toolbox, click Setup > Cluster Scaling. The Cluster Scaling page is displayed. The Load option is selected by default.
| Anchor | ||||
|---|---|---|---|---|
|
...
Kyvos will provide the following scaling modes for Load-based scaling:
Managed: In Managed scaling, Kyvos intelligently manages the cluster capacity to scale up and scale down.
Custom: In Custom scaling, you can set up rules based on your environment's usage patterns. Currently, the custom scaling mode supports CPU and Memory utilization-based scaling. When the CPU or memory load condition meets the configured parameters, the Query Engine cluster can be scaled up or down.
...
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
Note
|
Points to know
From Kyvos 2023.2 onwards, you can specify the time (in minutes) to hold the queries when query engines are started by using the QE_STARTUP_QUERY_HOLD_TIME property. Note that if the query engines become active before the configured time, the query will be served; otherwise, it will fail.
Upon completion of the Change Cluster State schedule, the load-based rules will be implemented automatically if they have been saved. If no rules have been saved on the Load screen, the cluster will run using the Change Cluster State capacity.
The scale-down rule implements when the cluster runs at full capacity. The Query Engines can scale down either from full to moderate capacity or from full to low In the future, it will be possible to scale the cluster even further. For instance, if the cluster was previously scaled down from maximum to moderate capacity, it can be scaled down again to the next lower capacity. Similarly, it can also be scaled up to increase its capacity.
If the query engine scales down to moderate capacity, you cannot further scale down the Query Engine to low capacity.The Kyvos cluster and the Query Engines automatically scale up at full capacity due to for any MOLAP query.
The Query Engines do not start for any ROLAP queries.
The scale-down duration cannot be less than 30 minutes.
The duration to shut down the query engine must be at least 30 minutes greater than the scale-down duration.
If the cluster is down and a query is executed, the first query triggers the cluster startup process, and all queries fail until the cluster is up and running. In this case, the following messages are displayed:
Message 1: "Could not serve the query as Query Engine Cluster is not available. Query Engine is launched. Please try after some time."
Message 2: "Could not serve the query as Query Engine Cluster is starting. Please try after some time."
During the transitioning period of Query Engines; such as scale-up, scale-down, or shut down; you can design and refine the semantic model because the Coordination Master is always up and running .
The following tables specify the approximate time required to complete the process during the transitioning period.
...
Select whether the service should remain online or offline.
Click to select a query engine capacity.
Click Change Now.
The Schedule entry is displayed in the schedule.
Subscribe to notifications
Click the Actions menu (...) located in the upper right corner of a cluster scaling page, and then click Subscribe Cluster Events to subscribe to receive notifications for cluster events. These events include the cluster shutting down as per schedule, the cluster state scaling down due to Cluster scheduling, all query engines being up and in a running state, the cluster state scaling down, entity modifications, or a license expiring soon.
You can set up notifications and subscriptions as needed.
...