Explanation on options related to Workflow High Availability (WKFHA)
This article explains the key options related to Workflow High Availability (WKFHA) in Adobe Campaign, specifically:
- WKFHA
- WKFHA_DelayedStartBatchSize
- WKFHA_LimitWFConcurrentRun
These options are designed to optimize workflow execution, control resource usage, and ensure fair load distribution across containers.
Description description
1. WKFHA (Workflow High Availability)
Description:
WKFHA refers to the set of features and options that enable high availability and fair load distribution for workflows in Adobe Campaign. When enabled, it helps manage how workflows are started and distributed across available containers, preventing resource spikes and ensuring system stability.
Key Points:
- Ensures workflows are distributed fairly across containers.
- Prevents overloading any single container.
- Works in conjunction with other guardrail options to control workflow concurrency and startup behavior.
2. WKFHA_DelayedStartBatchSize
Description:
This option controls the number of workflows that can be started immediately on a container, with subsequent batches delayed to avoid memory spikes.
Behavior:
-
If set to 4 (recommended optimum value for memory control)
For eg:
- On two containers, 8 workflows (4 per container) start immediately.
- The next batch of 8 starts after 20 seconds, and so on.
- After 60 seconds, a total of 32 workflows would be executing.
-
Setting the value to 0 disables this guardrail (no delay in starting workflows).
Purpose:
To control startup memory spikes when multiple workflows are started simultaneously.
3. WKFHA_LimitWFConcurrentRun
Description:
This option limits the number of workflows that can run concurrently on a container.
Behavior:
-
When the limit is reached, new workflows are queued and will not start until running workflows finish.
-
Helps prevent resource exhaustion and ensures system stability.
For eg: The default value is 20. For example, if there are 4 containers, the total number of concurrent workflows will be 80.
Resolution resolution
Additional Notes
- These options are especially relevant in environments with high workflow volume or multiple containers.
- Adjusting these values should be done carefully to balance performance and resource usage.
- Disabling guardrails (setting batch size to 0) may lead to memory spikes and instability.