Managing your System

• Workflow authors can limit the instances of parallel workflow execution globally across all runtimes. Set the new workflow header scheduledExecutionLimit to a static integer to set the limit for concurrent executing workflows.

• System admins can change load thresholds and batch sizes via dynamic properties without restarting a runtime. Every 30 seconds, the services re-read the dynamic properties. First, the property {runtimeNodeId}.{propertyName} is checked, which allows each runtime node to be configured differently. If the node-specific property doesn't exist, {propertyName} is checked. To set the values on specific runtimes, prepend the tuning parameter with the runtime's hostname / IP address. For example a runtime running on my network at 10.30.50.147:9090 would have the following example setting configured:

KEY 10.30.50.147:9090.high.load.cpu.threshold VALUE 80

The properties for the dynamic load service are (default value after the colon). Each of these can now be configured on a per host basis dynamically.

low.load.cpu.threshold:65.0medium.load.cpu.threshold:75.0high.load.cpu.threshold:90.0low.load.batch.allotment:5medium.load.batch.allotment:3high.load.batch.allotment:1default.load.batch.allotment:0