=clu #13802 Introduce max-total-nr-of-instances for cluster aware routers
This commit is contained in:
parent
12bee9433e
commit
bc13e1b4c2
23 changed files with 77 additions and 41 deletions
|
|
@ -155,6 +155,21 @@ In order to make cluster routers smarter about when they can start local routees
|
|||
In case you have implemented a custom Group you will have to update the method's signature,
|
||||
however the implementation can remain the same if you don't need to rely on an ActorSystem in your logic.
|
||||
|
||||
Cluster aware router max-total-nr-of-instances
|
||||
==============================================
|
||||
|
||||
In 2.3.x the deployment configuration property ``nr-of-instances`` was used for
|
||||
cluster aware routers to specify total number of routees in the cluster.
|
||||
This was confusing, especially since the default value is 1.
|
||||
|
||||
In 2.4.x there is a new deployement property ``cluster.max-total-nr-of-instances`` that
|
||||
defines total number of routees in the cluster. By default ``max-total-nr-of-instances``
|
||||
is set to a high value (10000) that will result in new routees added to the router when nodes join the cluster.
|
||||
Set it to a lower value if you want to limit total number of routees.
|
||||
|
||||
For backwards compatibility reasons ``nr-of-instances`` is still used if defined by user,
|
||||
i.e. if defined it takes precedence over ``max-total-nr-of-instances``.
|
||||
|
||||
Logger names use full class name
|
||||
================================
|
||||
Previously, few places in akka used "simple" logger names, such as ``Cluster`` or ``Remoting``.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue