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

=doc #24688 link to akka cluster bootstrap in docs (#24693)

Browse source 
* =doc #24688 link to akka cluster bootstrap in docs

* amend
This commit is contained in:
Konrad `ktoso` Malawski 2018-03-13 08:40:49 +09:00 • committed by GitHub
parent d03d8fdd7e
commit ff5ee68e72
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 13 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

20
akka-docs/src/main/paradox/cluster-usage.md
View file

@ -88,6 +88,12 @@ The source code of this sample can be found in the
## Joining to Seed Nodes ## Joining to Seed Nodes
@@@ note
When starting clusters on cloud systems such as Kubernetes, AWS, Google Cloud, Azure, Mesos or others which maintain
DNS or other ways of discovering nodes, you may want to use the automatic joining process implemented by the open source
[Akka Cluster Bootstrap](https://developer.lightbend.com/docs/akka-management/current/bootstrap.html) module.
@@@
You may decide if joining to the cluster should be done manually or automatically You may decide if joining to the cluster should be done manually or automatically
to configured initial contact points, so-called seed nodes. After the joining process to configured initial contact points, so-called seed nodes. After the joining process
the seed nodes are not special and they participate in the cluster in exactly the same the seed nodes are not special and they participate in the cluster in exactly the same
@ -112,13 +118,14 @@ This can also be defined as Java system properties when starting the JVM using t
-Dakka.cluster.seed-nodes.1=akka.tcp://ClusterSystem@host2:2552 -Dakka.cluster.seed-nodes.1=akka.tcp://ClusterSystem@host2:2552
``` ```
Such configuration is typically created dynamically by external tools, see for example: Instead of manually configuring seed nodes, which is useful in development or statically assigned node IPs, you may want
to automate the discovery of seed nodes using your cloud providers or cluster orchestrator, or some other form of service
* [Deploying clustered Akka applications on Kubernetes](http://developer.lightbend.com/guides/k8-akka-cluster/) discovery (such as managed DNS). The open source Akka Management library includes the
* [ConstructR](https://github.com/hseeberger/constructr) [Cluster Bootstrap](https://developer.lightbend.com/docs/akka-management/current/bootstrap.html) module which handles
just that. Please refer to its documentation for more details.
The seed nodes can be started in any order and it is not necessary to have all The seed nodes can be started in any order and it is not necessary to have all
seed nodes running, but the node configured as the first element in the `seed-nodes` seed nodes running, but the node configured as the **first element** in the `seed-nodes`
configuration list must be started when initially starting a cluster, otherwise the configuration list must be started when initially starting a cluster, otherwise the
other seed-nodes will not become initialized and no other node can join the cluster. other seed-nodes will not become initialized and no other node can join the cluster.
The reason for the special first seed node is to avoid forming separated islands when The reason for the special first seed node is to avoid forming separated islands when
@ -176,8 +183,7 @@ be allowed to join.
@@@ note @@@ note
The name of the `ActorSystem` must be the same for all members of a cluster. The name is given The name of the `ActorSystem` must be the same for all members of a cluster. The name is given when you start the `ActorSystem`.
when you start the `ActorSystem`.
@@@ @@@