raboof/pekko
1
0
Fork 0
Code Issues Pull requests Projects Releases 6 Packages Wiki Activity Actions 10

Update cluster.md (#30352)

Browse source
This commit is contained in:
marcoderama 2021-07-06 02:05:03 -07:00 • committed by GitHub
parent edf68f32ba
commit 75031c00cb
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

10
akka-docs/src/main/paradox/typed/cluster.md
View file

@ -148,8 +148,8 @@ Please refer to its documentation for more details.
#### Joining configured seed nodes #### Joining configured seed nodes
When a new node is started it sends a message to all seed nodes and then sends join command to the one that When a new node is started it sends a message to all seed nodes and then sends a join command to the one that
answers first. If no one of the seed nodes replied (might not be started yet) answers first. If none of the seed nodes replies (might not be started yet)
it retries this procedure until success or shutdown. it retries this procedure until success or shutdown.
You can define the seed nodes in the @ref:[configuration](#configuration) file (application.conf): You can define the seed nodes in the @ref:[configuration](#configuration) file (application.conf):
@ -169,7 +169,7 @@ This can also be defined as Java system properties when starting the JVM using t
When a new node is started it sends a message to all configured `seed-nodes` and then sends a join command to the When a new node is started it sends a message to all configured `seed-nodes` and then sends a join command to the
one that answers first. If none of the seed nodes replied (might not be started yet) it retries this procedure one that answers first. If none of the seed nodes replies (might not be started yet) it retries this procedure
until successful or shutdown. until successful or shutdown.
The seed nodes can be started in any order. It is not necessary to have all The seed nodes can be started in any order. It is not necessary to have all
@ -369,14 +369,14 @@ configuration descriptions, default values and options.
A common use case is to start actors after the cluster has been initialized, A common use case is to start actors after the cluster has been initialized,
members have joined, and the cluster has reached a certain size. members have joined, and the cluster has reached a certain size.
With a configuration option you can define required number of members With a configuration option you can define the required number of members
before the leader changes member status of 'Joining' members to 'Up'.: before the leader changes member status of 'Joining' members to 'Up'.:
``` ```
akka.cluster.min-nr-of-members = 3 akka.cluster.min-nr-of-members = 3
``` ```
In a similar way you can define required number of members of a certain role In a similar way you can define the required number of members of a certain role
before the leader changes member status of 'Joining' members to 'Up'.: before the leader changes member status of 'Joining' members to 'Up'.:
``` ```