Versions Compared

Key

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

Applies to: (tick) Kyvos Enterprise  (tick) Kyvos Cloud (SaaS on AWS) (tick) 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 no queries are being executedthe cluster is under usage. Additionally, you can set a rule to automatically shut down the Query Engines and BI Servers if no query traffic is received the cluster is not in use for a specified period of time. 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 a specified number of queries are executed the cluster utilization exceeds over a defined time period. 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.

...

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 load condition meets the configured parameters, the Query Engine cluster can be scaled up or down.

On this page, you can specify rules to scale down or scale up the query engines, as well as set rules to shut down or start the BI Servers and query engines.

Panel
panelIconIdatlassian-note
panelIcon:note:
bgColor#DEEBFF

Note

  • The capacity of the BI Servers cannot be changed.

  • All BI Servers can be shut down except the Coordination Master. It is required to provide a response to a query. If there is only one BI Server, this BI Server is treated as the Coordination Master.

  • The Settings option and Add Schedule option are disabled on the Load screen. You can set the default settings for the query engine cluster or create a new schedule using the Schedule option displayed on the Cluster Scheduling page. See the Creating schedule-based scaling section for more details. 

  • You can view on-screen notifications that provide you with timely information about the state of the cluster. 

  • When you scale down the Query Engines, you reduce the capacity of the node, including the number of cores and memory. Conversely, when you scale up the Query Engines, you increase the capacity of the node by adding more cores and memory.

Cluster Scaling page to set load-based scaling 

To set a load-based scheduling, perform the following steps.

  1. From the Toolbox, click Setup > Cluster Scaling. The Cluster Scaling page is displayed.

    Image Removed

...

  • .

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 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 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. 

Aura tab collection
paramsJTdCJTIyZ2VuZXJhbCUyMiUzQSU3QiUyMnRhYlNwYWNpbmclMjIlM0EwJTJDJTIydGFiV2lkdGglMjIlM0ExMDAlMkMlMjJ0YWJIZWlnaHQlMjIlM0E1MCUyQyUyMmRpcmVjdGlvbiUyMiUzQSUyMmhvcml6b250YWwlMjIlN0QlMkMlMjJjb250ZW50JTIyJTNBJTdCJTIyYmFja2dyb3VuZENvbG9yJTIyJTNBJTdCJTIyY29sb3IlMjIlM0ElMjIlMjNmZmYlMjIlN0QlMkMlMjJib3JkZXIlMjIlM0ElN0IlMjJzdHlsZSUyMiUzQSUyMnNvbGlkJTIyJTJDJTIyd2lkdGglMjIlM0ExJTJDJTIydG9wJTIyJTNBdHJ1ZSUyQyUyMmJvdHRvbSUyMiUzQXRydWUlMkMlMjJsZWZ0JTIyJTNBdHJ1ZSUyQyUyMnJpZ2h0JTIyJTNBdHJ1ZSUyQyUyMmNvbG9yJTIyJTNBJTdCJTIybGlnaHQlMjIlM0ElMjIlMjNjY2NlY2YlMjIlN0QlN0QlMkMlMjJwYWRkaW5nJTIyJTNBJTdCJTIydG9wJTIyJTNBMTAlMkMlMjJyaWdodCUyMiUzQTEwJTJDJTIyYm90dG9tJTIyJTNBMTAlMkMlMjJsZWZ0JTIyJTNBMTAlN0QlN0QlMkMlMjJhY3RpdmUlMjIlM0ElN0IlMjJiYWNrZ3JvdW5kQ29sb3IlMjIlM0ElN0IlMjJjb2xvciUyMiUzQSU3QiUyMmxpZ2h0JTIyJTNBJTIyJTIzZjU4MjI3JTIyJTdEJTdEJTJDJTIydGV4dCUyMiUzQSU3QiUyMmZvbnRTaXplJTIyJTNBMTYlMkMlMjJjb2xvciUyMiUzQSU3QiUyMmxpZ2h0JTIyJTNBJTIyJTIzMDAwMDAwJTIyJTdEJTJDJTIydGV4dEFsaWduJTIyJTNBJTIybGVmdCUyMiUyQyUyMmZvbnRXZWlnaHQlMjIlM0ElMjJib2xkJTIyJTdEJTdEJTJDJTIyaG92ZXIlMjIlM0ElN0IlMjJiYWNrZ3JvdW5kQ29sb3IlMjIlM0ElN0IlMjJjb2xvciUyMiUzQSUyMiUyM2RmZTFlNiUyMiU3RCUyQyUyMnRleHQlMjIlM0ElN0IlMjJmb250U2l6ZSUyMiUzQTE4JTJDJTIyY29sb3IlMjIlM0ElMjIlMjM1ZTZjODQlMjIlMkMlMjJ0ZXh0QWxpZ24lMjIlM0ElMjJsZWZ0JTIyJTJDJTIyZm9udFdlaWdodCUyMiUzQSUyMmxpZ2h0ZXIlMjIlN0QlN0QlMkMlMjJpbmFjdGl2ZSUyMiUzQSU3QiUyMmJhY2tncm91bmRDb2xvciUyMiUzQSU3QiUyMmNvbG9yJTIyJTNBJTIyJTIzZjRmNWY3JTIyJTdEJTJDJTIydGV4dCUyMiUzQSU3QiUyMmZvbnRTaXplJTIyJTNBMTYlMkMlMjJjb2xvciUyMiUzQSUyMiUyMzVlNmM4NCUyMiUyQyUyMnRleHRBbGlnbiUyMiUzQSUyMmxlZnQlMjIlMkMlMjJmb250V2VpZ2h0JTIyJTNBJTIybGlnaHRlciUyMiU3RCUyQyUyMmJvcmRlciUyMiUzQSU3QiUyMnRvcCUyMiUzQXRydWUlMkMlMjJsZWZ0JTIyJTNBdHJ1ZSUyQyUyMnJpZ2h0JTIyJTNBdHJ1ZSUyQyUyMmJvdHRvbSUyMiUzQXRydWUlMkMlMjJ3aWR0aCUyMiUzQTElMkMlMjJzdHlsZSUyMiUzQSUyMnNvbGlkJTIyJTJDJTIyY29sb3IlMjIlM0ElN0IlMjJsaWdodCUyMiUzQSUyMiUyM2NjY2VjZiUyMiU3RCU3RCU3RCU3RA==
Aura tab
summaryAWS
paramsJTdCJTIydGl0bGUlMjIlM0ElMjJBV1MlMjIlN0Q=

The process with the number of Query Engine =10

The time required for Load-based scaling

scale up

16 mins.

scale down

12 mins.

startup

4 mins.

Aura tab
summaryAzure
paramsJTdCJTIydGl0bGUlMjIlM0ElMjJBenVyZSUyMiU3RA==

The process with the number of Query Engine =7

The previous time required for Load-based scaling

New time required for Load-based scaling

Scale up

15-19 minutes

11-13 minutes

Scale down

15-19 minutes

11-13 minutes

Startup

8-10 minutes

8-10 minutes

Aura tab
summaryGCP
paramsJTdCJTIydGl0bGUlMjIlM0ElMjJHQ1AlMjIlN0Q=

The process with the number of Query Engine =10

The time required for Load-based scaling

scale up

4-5 mins.

scale down

5-6 mins.

startup

3-4 mins.

 To set the scaling rules for the query enginesmodes for Load-Based scaling, perform the following steps. 

...

  1. On the page, select the Load option. The Load page is displayed. 

    Image Removedimage-20240401-085154.pngImage Added
  2. To scale down the query engines, you must set the following rules:set the scaling mode, select one of the following:

    1. Managed: Select the capacity option as Low, Moderate, High , or Low Full from the list , and then set the time. You can also set the Shutdown rule for the query engines if no query is fired for a defined period. 

    2. Select Query Engines or BI Servers and Query Engines from the list, and then set the time. 

    If you want to scale up the query engines, you must set the following rules:
    1. to start Query Engine and BI Server when any query is fired.  

    2. Custom: To set scale up and scale down the query engines and BI Server.

      • To scale up,   

        1. To start the BI Servers and query engines, select the capacity option as Low, Moderate, High

      ,
        1. or

      Low
        1. Full from the list when any query is fired. 

      To
        1. Enter a percentage to scale up the

      query engines with the desired capacity, you need to specify the number of queries and the duration for which the query engines should be scaled up.
    Click Save
        1. cluster if CPU and memory utilization threshold goes above the specified percentage. Also, specify the number of data points and the total number of data points to set.

      • To scale down,

        1. To shut down the BI Server and/or Query Engine, when no queries is fired for specified period of time.

        2. Enter a percentage to scale down the cluster if CPU and memory utilization threshold remains below the specified percentage. Also, specify the number of data points and the total number of data points to set.

  3. Click Save. The load-based scaling mode is set.

Panel
panelIconIdatlassian-note
panelIcon:note:
bgColor#DEEBFF

NOTE

A data point is information on resource utilization captured every 30 seconds.

Changing cluster state 

You can change the cluster capacity as required. This change comes into effect immediately and overrides any existing schedules or rules. 

...

  1. Select whether the service should remain online or offline.

  2. Click to select a query engine capacity. 

  3. 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.

...