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 34 Next »

Private_Edition_flag.png

The following guide can be used to assist you when creating your unique batch scaling solution. An important thing to remember is that you cannot mix standard agents with scaling agents in the same workflows. Workflows with standard agents save the state in Usage Engine and workflows with batch agents save the state in Kafka.

Creating a scalable solution (example)

These are high-level steps to creating a scalable batch solution in Usage Engine. The following example solution is made up of several profiles including the newly created Partition Profile (4.3) and Scalable Inter Workflow Profile (4.3), and two workflow types, Batch Scaling Collection and Batch Scaling Processing.

  1. Choose your scaling factor, this will be the MAX no. WFs that can effectively cooperate to process a batch. This is an important choice and will be difficult to change once your WFs are in production.

Warning!
Try to pick a Max Scale Factor that is divisible by many other numbers, like 6 or 12. You need to ensure that it is high enough to handle the data coming in, but not so high that you will overload resources.

  1. You must choose one or more fields in your UDRs that will be used to partition data. These fields may be based on a record group like a customer ID or an account number.

  2. Create a Partition Profile where you define your Max Scale Factor and your partitioning fields.

  3. Create the Aggregation, Duplicate UDR, and Scalable Inter Workflow profiles and link the Partition Profile created in Step 2 to each.

  4. Create your workflows.

    • Standard WFs to prep data for scaling by sending it to scalable IWF forwarder

    • Scalable processing WFs start with a Scalable IWF Collector.

Note!
When creating a scalable workflow you need to add the Kafka profile in the execution tab of the workflow properties.

Note!
You can include multiple Aggregation and Duplicate UDR agents within the same workflow. These agents can either share the same Partition Profile or use different Aggregation and Duplicate UDR Profiles. For instance, you might use different profiles if you need to apply a different ID field as the Key in storage.

Scaling Batch Workflows

Usage Engine will scale out and in and re-balance scalable batch workflows automatically and you can schedule when to start a scale-out or scale-in.

Deploying a scale-out configuration with ECDs:

Use https://infozone.atlassian.net/wiki/x/IgMkEg with Dynamic Workflows to define how to package a scale-out. See the tabs on https://infozone.atlassian.net/wiki/x/VgQkEg for more information.

You can schedule the ECD and workflow to start or stop at specific times, or, you can start them manually.

Scaling option

Description

Automatic Scaling

Based on a configured metric, for example, scaling starts when more than X number of UDRs are received for processing and stops when the received UDRs drop below this number.

Manual Scaling

There are two options for manual scaling;

  • Manually start the ECD and Workflow when you want them to begin.

  • Apply a fixed schedule for starting the ECD, for example, you can set the scaling to occur daily from 5:00pm until 10:00pm.

  • No labels