AdaptiveLoadBalancingPool
Related Doc:
package metrics
Java API
Java API
decides what probability to use for selecting a routee, based on remaining capacity as indicated by the node metrics
initial number of routees in the pool
decides what probability to use for selecting a routee, based on remaining capacity as indicated by the node metrics
initial number of routees in the pool
strategy for supervising the routees, see 'Supervision Setup'
dispatcher to use for the router head actor, which handles supervision, death watch and router management messages
decides what probability to use for selecting a routee, based on remaining capacity as indicated by the node metrics
initial number of routees in the pool
dispatcher to use for the router head actor, which handles supervision, death watch and router management messages
dispatcher to use for the router head actor, which handles supervision, death watch and router management messages
strategy for supervising the routees, see 'Supervision Setup'
strategy for supervising the routees, see 'Supervision Setup'
Setting the dispatcher to be used for the router head actor, which handles supervision, death watch and router management messages.
Uses the supervisor strategy of the given RouterConfig if this RouterConfig doesn't have one
Uses the supervisor strategy of the given RouterConfig if this RouterConfig doesn't have one
Setting the supervisor strategy to be used for the “head” Router actor.
A router pool that performs load balancing of messages to cluster nodes based on cluster metric data.
It uses random selection of routees based on probabilities derived from the remaining capacity of corresponding node.
The configuration parameter trumps the constructor arguments. This means that if you provide
nrOfInstancesduring instantiation they will be ignored if the router is defined in the configuration file for the actor being used.Supervision Setup
Any routees that are created by a router will be created as the router's children. The router is therefore also the children's supervisor.
The supervision strategy of the router actor can be configured with #withSupervisorStrategy. If no strategy is provided, routers default to a strategy of “always escalate”. This means that errors are passed up to the router's supervisor for handling.
The router's supervisor will treat the error as an error with the router itself. Therefore a directive to stop or restart will cause the router itself to stop or restart. The router, in turn, will cause its children to stop and restart.
decides what probability to use for selecting a routee, based on remaining capacity as indicated by the node metrics
initial number of routees in the pool
strategy for supervising the routees, see 'Supervision Setup'
dispatcher to use for the router head actor, which handles supervision, death watch and router management messages