Select the Load Balancing Strategy for preferred scalability and redundancy.
The Load Balancing Strategy is used if you set the number of collectors to more than 1. There are two strategies:
Static: LoadIDs from the UDRs are used to determine how data should be distributed via the workflows. See Workflow Bridge Example Real-Time to Real-Time Scenario with Load Balancing /wiki/spaces/MD/pages/2949137 for how to use this.
Dynamic: Select to distribute the load over all the available collectors. The LoadID from the UDR is used virtually and is not connected to any hardware at the collecting side. The LoadID settings of the workflows will be ignored during load balancing.
When selecting Dynamic, another field called Virtual Destinations is displayed. The default setting of the Virtual Destination field is 1024. The LoadIDs in the UDR are mapped to virtual destinations distributed evenly on available consumer instances. The LoadIDs set in the Workflow Table are ignored. For instance, if Virtual Destinations is set to 1024, the UDR's LoadIDs must be populated with values from 0-1023.
The Workflow Bridge engine will create the amount of virtual destinations that you have specified in the LoadID field. If starting another workflow, the virtual destinations will be redistributed evenly between the available workflows.
In most cases the default setting 1024 of Virtual Destinations is sufficient and will work fine. In case you want to change this, it should be set as a number that is the power of two, such as 512, 1024, or 2048. The number of destinations may vary, so make sure the number is set high enough to get a decent distribution.
Note |
---|
|
The Virtual Destinations field is only available if you have set Load Balancing Strategy to Dynamic. |