...
Finally, you will need to select an identifier that the workflow will use to distribute the UDRs. Typically, this would be a field based on the record group like a customer ID or an account number. You can also create and populate a field using APL, see https://infozone.atlassian.net/wiki/x/xeckEg. AoB8Fw
Note!
When creating a scalable workflow you need to add the Kafka profile in the execution tab of the workflow properties.
...
Parameter | Comment | ||
|---|---|---|---|
ID Field | Defines how to match a UDR to a partition. | ||
Max Scale Factor - this is located in the Partition profile config. | Number of partitions, which is the same as maximum number of workflows that can execute in parallel. - this means that there can be fewer workflows - but not more. Note! If any of the parameters need to be changed, it is considered a new configuration, and they need to start with empty topics.
|
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.
...
Use the regular https://infozone.atlassian.net/wiki/x/IgMkEg definition using ‘Dynamic Workflows’ Dynamic Workflows https://infozone.atlassian.net/wiki/x/VgQkEg to define how to package a scale-out. You need to define when these ECDs will activate.
...
.
...
A Processing Workflow scales with 3 extra Workflows per ECD.
...
Or combine the above into the same ECD.
Scheduling a scale-out configuration:
You can schedule the ECD and workflow to start or stop at specific times, alternatively, these can also be started manually. This is configured in… If no schedule for scaling is created, the system will scale automatically based on metrics.
Add an image of the setting for the manual schedule.
Use this table to explain the settings in the image.
See the above links for more information.
Automatic Scaling | Manual Scaling |
|---|---|
|
|
| Warning |
|---|
Questions: Assumedly a scaling solution will contain multiple workflows and based on the above these workflows can be scheduled to be started at specific times or based on metrics? How does it being based on metrics work? does this need to be configured somewhere? The key difference for customers is that scaling workflows are quicker/more efficient at processing data than regular workflows? It’s not more automated in general but it is automatic at being efficient. (that sounds weird, but I think I understand what I mean.) This is why the metric question is interesting.. because sometimes a customer won’t know what times they’ll need to scale workflows. |
...
|