shard coordinator should wait until min-members regions registered, #21194
This commit is contained in:
parent
1ff1f5edee
commit
141318e60a
8 changed files with 255 additions and 12 deletions
|
|
@ -216,6 +216,17 @@ no matter how ``State Store Mode`` is set.
|
|||
The ``ddata`` mode is considered as **“experimental”** as of its introduction in Akka 2.4.0, since
|
||||
it depends on the experimental Distributed Data module.
|
||||
|
||||
Startup after minimum number of members
|
||||
---------------------------------------
|
||||
|
||||
It's good to use Cluster Sharding with the Cluster setting ``akka.cluster.min-nr-of-members`` or
|
||||
``akka.cluster.role.<role-name>.min-nr-of-members``. That will defer the allocation of the shards
|
||||
until at least that number of regions have been started and registered to the coordinator. This
|
||||
avoids that many shards are allocated to the first region that registers and only later are
|
||||
rebalanced to other nodes.
|
||||
|
||||
See :ref:`min-members_java` for more information about ``min-nr-of-members``.
|
||||
|
||||
Proxy Only Mode
|
||||
---------------
|
||||
|
||||
|
|
|
|||
|
|
@ -325,6 +325,8 @@ and it is typically defined in the start script as a system property or environm
|
|||
|
||||
The roles of the nodes is part of the membership information in ``MemberEvent`` that you can subscribe to.
|
||||
|
||||
.. _min-members_java:
|
||||
|
||||
How To Startup when Cluster Size Reached
|
||||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue