Applies to: Kyvos Enterprise Kyvos Cloud (SaaS on AWS) Kyvos AWS Marketplace
...
When the cluster usage pattern is not fixed, you must use load-based scaling. This type of scaling allows you to automatically scale up or scale down the query engines based on the resource utilization of the Query Engine instances. By configuring cluster scaling, you can enhance the utilization of your cloud cluster and save on compute costs.
From Kyvos 2024.2 onwards, scaling is implemented based on the CPU 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.
...
Panel | ||||||
---|---|---|---|---|---|---|
| ||||||
Note
|
...
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."
By default, the queries fail until Query Engines are started. If you want to hold the queries when query engines are down, you can specify the time (in minutes) for holding queries by using the QE_STARTUP_QUERY_HOLD_TIME property.
Ensure that if the query engines become active before the configured time, the query will be served; otherwise, it will fail.The Query Engines do not start for any ROLAP queries.
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.
...