Engine Balancer Configuration

The Engine balancer to use: Weight-Based or Home/Shared.

The amount of time, in seconds, between balancing episodes. (Previously called the Poll Period.)

The amount of time in seconds that an Engine waits to finish a task before logging off.

The maximum time to wait for Broker’s reply for balancer data queries. The value is in milliseconds.

If true, Engine logoffs do not restart the JVM unless needed by a home Broker. This enables them to retain state and log in faster.

The fraction of extra Engines that moves to another Broker on a balance. This can be set to less than 1 to dampen Engine movement. For example, if the fraction is 0.5 and the balancer determines that a Broker has eight extra Engines, it moves four on the first balance. Assuming those Engines move, on the next balance it determines that there are four extra and moves two, and so on.

The maximum number of Engines that can move to another Broker on a rebalance. The maximum applies over the entire grid. For example, if this property is set to 100 and the balancer determines to rebalance 200 Engines (after taking Engine Balance Fraction into account), then only 100 Engines are actually rebalanced.

The maximum number of service discriminators to consider when reporting balance data from each Broker.

If Broker Routing properties are used when the Sharing balancer is enabled. Under most circumstances, when using the Sharing balancer, it is best not to also use routing.