Control the executor function with the dscontrol rule command.
>>-dscontrol--rule--+-add--cluster@port@rule--type--+-active-+--options-+->< | '-true---' | +-dropserver--cluster@port@rule--server-------------+ +-remove--cluster@port@rule-------------------------+ +-report--cluster@port@rule-------------------------+ +-set--cluster@port@rule--options-------------------+ +-status--------------------------------------------+ '-useserver--cluster@port@rule--server+s2+----------'
dscontrol rule add @80@RuleA type typeSeparate additional clusters with a plus sign (+).
dscontrol rule add clusterA@@RuleA type typeSeparate additional ports with a plus sign (+).
If you do not specify the priority of the first rule you add, Load Balancer will set it to 1 by default. When a subsequent rule is added, by default its priority is calculated to be 10 + the current lowest priority of any existing rule. For example, assume you have an existing rule whose priority is 30. You add a new rule and set its priority at 25 (which, remember, is a higher priority than 30). Then you add a third rule without setting a priority. The priority of the third rule is calculated to be 40 (30 + 10).
Evaluate servers within the rule
Evaluate servers on the port
Using the two rules described above, if you set the evaluate option to port for the first rule (evaluate rule's condition across all the servers on the port), when traffic exceeds the threshold of that rule, traffic is sent to the "site busy" server associated to the second rule. The first rule measures all server traffic (including the "site busy" server) on the port to determine whether the traffic exceeds the threshold. As congestion decreases for the servers associated to the first rule, an unintentional result may occur where traffic continues to the "site busy" server because traffic on the port still exceeds the threshold of the first rule.
dscontrol rule add 130.40.52.153@80@pool2 type active beginrange 250 endrange 500
dscontrol rule add 130.40.52.153@80@jamais type true priority 100